Cancellation and Replacement of PUSCH

ABSTRACT

Apparatuses, systems, and methods for cancellation and/or replacement of PUSCHs. A user equipment device (UE) may configure a first PUSCH and a second PUSCH, where the first PUSCH may correspond to a configured grant and where the second PUSCH may correspond to a configured grant or scheduled by a PDCCH on a serving cell. The UE may determine that at least one transmission occasion associated with the first PUSCH overlaps in time with at least one transmission occasion associated with the second PUSCH. The UE may drop transmissions scheduled for the second PUSCH, e.g., based on determining that a priority of the first PUSCH is higher than a priority of the second PUSCH, e.g., starting with a first symbol of a repetition of the second PUSCH which overlaps in time with one or more repetitions of the first PUSCH.

PRIORITY DATA

This application is a continuation of U.S. application Ser. No.17/396,161 titled “Cancellation and Replacement of PUSCH”, filed Aug. 6,2021, which claims benefit of priority to U.S. Provisional ApplicationSer. No. 63/062,146, titled “Cancellation and Replacement of PUSCH”,filed Aug. 6, 2020, which is hereby incorporated by reference in itsentirety as though fully and completely set forth herein.

The claims in the instant application are different than those of theparent application and/or other related applications. The Applicanttherefore rescinds any disclaimer of claim scope made in the parentapplication and/or any predecessor application in relation to theinstant application. Any such previous disclaimer and the citedreferences that it was made to avoid, may need to be revisited. Further,any disclaimer made in the instant application should not be read intoor against the parent application and/or other related applications.

FIELD

The invention relates to wireless communications, and more particularlyto apparatuses, systems, and methods for cancellation and/or replacementof physical uplink shared channels (PUSCHs) with differing priorities,e.g., for ultra-reliable low-latency communication (URLLC) and/orenhanced URLLC (eURLLC).

DESCRIPTION OF THE RELATED ART

Wireless communication systems are rapidly growing in usage. In recentyears, wireless devices such as smart phones and tablet computers havebecome increasingly sophisticated. In addition to supporting telephonecalls, many mobile devices now provide access to the internet, email,text messaging, and navigation using the global positioning system(GPS), and are capable of operating sophisticated applications thatutilize these functionalities.

Long Term Evolution (LTE) has become the technology of choice for themajority of wireless network operators worldwide, providing mobilebroadband data and high-speed Internet access to their subscriber base.LTE defines a number of downlink (DL) physical channels, categorized astransport or control channels, to carry information blocks received frommedium access control (MAC) and higher layers. LTE also defines a numberof physical layer channels for the uplink (UL).

For example, LTE defines a Physical Downlink Shared Channel (PDSCH) as aDL transport channel. The PDSCH is the main data-bearing channelallocated to users on a dynamic and opportunistic basis. The PDSCHcarries data in Transport Blocks (TB) corresponding to a MAC protocoldata unit (PDU), passed from the MAC layer to the physical (PHY) layeronce per Transmission Time Interval (TTI). The PDSCH is also used totransmit broadcast information such as System Information Blocks (SIB)and paging messages.

As another example, LTE defines a Physical Downlink Control Channel(PDCCH) as a DL control channel that carries the resource assignment forUEs that are contained in a Downlink Control Information (DCI) message.Multiple PDCCHs can be transmitted in the same subframe using ControlChannel Elements (CCE), each of which is a nine set of four resourceelements known as Resource Element Groups (REG). The PDCCH employsquadrature phase-shift keying (QPSK) modulation, with four QPSK symbolsmapped to each REG. Furthermore, 1, 2, 4, or 8 CCEs can be used for aUE, depending on channel conditions, to ensure sufficient robustness.

Additionally, LTE defines a Physical Uplink Shared Channel (PUSCH) as aUL channel shared by all devices (user equipment, UE) in a radio cell totransmit user data to the network. The scheduling for all UEs is undercontrol of the LTE base station (enhanced Node B, or eNB). The eNB usesthe uplink scheduling grant (DCI format 0) to inform the UE aboutresource block (RB) assignment, and the modulation and coding scheme tobe used. PUSCH typically supports QPSK and quadrature amplitudemodulation (QAM). In addition to user data, the PUSCH also carries anycontrol information necessary to decode the information, such astransport format indicators and multiple-in multiple-out (MIMO)parameters. Control data is multiplexed with information data prior todigital Fourier transform (DFT) spreading.

A proposed next telecommunications standard moving beyond the currentInternational Mobile Telecommunications-Advanced (IMT-Advanced)Standards is called 5th generation mobile networks or 5th generationwireless systems, or 5G for short (otherwise known as 5G-NR for 5G NewRadio, also simply referred to as NR). 5G-NR may provide a highercapacity for a higher density of mobile broadband users, also supportingdevice-to-device, ultra-reliable, and massive machine typecommunications with lower latency and/or lower battery consumption.Further, the 5G-NR may allow for more flexible UE scheduling as comparedto current LTE. Consequently, efforts are being made in ongoingdevelopments of 5G-NR to take advantage of higher throughputs possibleat higher frequencies.

SUMMARY

Embodiments relate to wireless communications, and more particularly toapparatuses, systems, and methods for cancellation and/or replacement ofphysical uplink shared channels (PUSCHs) with differing priorities,e.g., for ultra-reliable low-latency communication (URLLC) and/orenhanced URLLC (eURLLC).

For example, a user equipment device (UE) may be configured to configurea first PUSCH and a second PUSCH, e.g., the UE may determine resourcesfor transmission on the first PUSCH and the second PUSCH. The firstPUSCH may correspond to a configured grant. The second PUSCH maycorrespond to a configured grant or may be scheduled by a physicaldownlink control channel (PDCCH) on a serving cell. Thus, the UE mayconfigure the first PUSCH (e.g., determine resources for transmission onthe first PUSCH) based on the configured grant. Similarly, the UE mayconfigure the second PUSCH (e.g., determine resources for transmissionon the second PUSCH) based on the schedule provided by the PDCCH on theserving cell (e.g., a dynamic grant) and/or another configured grant. Inother words, the UE may prepare transmission of first data on a firstPUSCH resource based on the configured grant. Similarly, the UE mayprepare transmission of second data on a second PUSCH resource based onthe schedule provided by the PDCCH on the serving cell and/or anotherconfigured grant. Additionally, the UE may be configured to determinethat at least one transmission occasion associated with the first PUSCHoverlaps in time with at least one transmission occasion associated withthe second PUSCH. Further, the UE may be configured to drop (e.g.,based, at least in part, on a priority of the first PUSCH) transmissions(e.g., one or more transmissions) scheduled for the second PUSCH. Forexample, the UE may drop transmissions scheduled for the second PUSCHbased, at least in part, on determining that the priority of the firstPUSCH is higher than a priority of the second PUSCH. T transmissionsscheduled for the second PUSCH may be dropped starting with a firstsymbol of a repetition of the second PUSCH which overlaps in time withone or more repetitions of the first PUSCH.

The techniques described herein may be implemented in and/or used with anumber of different types of devices, including but not limited tounmanned aerial vehicles (UAVs), unmanned aerial controllers (UACs), aUTM server, base stations, access points, cellular phones, tabletcomputers, wearable computing devices, portable media players, and anyof various other computing devices.

This Summary is intended to provide a brief overview of some of thesubject matter described in this document. Accordingly, it will beappreciated that the above-described features are merely examples andshould not be construed to narrow the scope or spirit of the subjectmatter described herein in any way. Other features, aspects, andadvantages of the subject matter described herein will become apparentfrom the following Detailed Description, Figures, and Claims.

BRIEF DESCRIPTION OF THE DRAWINGS

A better understanding of the present subject matter can be obtainedwhen the following detailed description of various embodiments isconsidered in conjunction with the following drawings, in which:

FIG. 1A illustrates an example wireless communication system accordingto some embodiments.

FIG. 1B illustrates an example of a base station (BS) and an accesspoint in communication with a user equipment (UE) device according tosome embodiments.

FIG. 2 illustrates an example simplified block diagram of a WLAN AccessPoint (AP), according to some embodiments.

FIG. 3 illustrates an example block diagram of a BS according to someembodiments.

FIG. 4 illustrates an example block diagram of a server according tosome embodiments.

FIG. 5A illustrates an example block diagram of a UE according to someembodiments.

FIG. 5B illustrates an example block diagram of cellular communicationcircuitry, according to some embodiments.

FIG. 6A illustrates an example of connections between an EPC network, anLTE base station (eNB), and a 5G NR base station (gNB).

FIG. 6B illustrates an example of a protocol stack for an eNB and a gNB.

FIG. 7A illustrates an example of a 5G network architecture thatincorporates both 3GPP (e.g., cellular) and non-3GPP (e.g.,non-cellular) access to the 5G CN, according to some embodiments.

FIG. 7B illustrates an example of a 5G network architecture thatincorporates both dual 3GPP (e.g., LTE and 5G NR) access and non-3GPPaccess to the 5G CN, according to some embodiments.

FIG. 8 illustrates an example of a baseband processor architecture for aUE, according to some embodiments.

FIG. 9 illustrates examples of dynamic grants colliding with configuredgrants.

FIG. 10 illustrates further examples of dynamic grants colliding withconfigured grants.

FIG. 11 illustrates an example of nested configured and dynamic grants.

FIGS. 12A-C illustrate examples of implementations of configuredgrant/dynamic grant collision handling.

FIG. 13 illustrates examples of possible treatments of collidingtransmissions, according to some embodiments.

FIGS. 14-16 illustrate examples of interleaving of a dynamic grant and aconfigured grant, according to some embodiments.

FIGS. 17-19 illustrate block diagrams of examples of methods forselection of physical uplink shared channels (PUSCHs) with differingpriorities, according to some embodiments.

While the features described herein may be susceptible to variousmodifications and alternative forms, specific embodiments thereof areshown by way of example in the drawings and are herein described indetail. It should be understood, however, that the drawings and detaileddescription thereto are not intended to be limiting to the particularform disclosed, but on the contrary, the intention is to cover allmodifications, equivalents and alternatives falling within the spiritand scope of the subject matter as defined by the appended claims.

DETAILED DESCRIPTION Acronyms

Various acronyms are used throughout the present disclosure. Definitionsof the most prominently used acronyms that may appear throughout thepresent disclosure are provided below:

-   -   3GPP: Third Generation Partnership Project    -   UE: User Equipment    -   RF: Radio Frequency    -   BS: Base Station    -   DL: Downlink    -   UL: Uplink    -   LTE: Long Term Evolution    -   NR: New Radio    -   5GS: 5G System    -   5GMM: 5GS Mobility Management    -   5GC/5GCN: 5G Core Network    -   IE: Information Element    -   CE: Control Element    -   MAC: Medium Access Control    -   SSB: Synchronization Signal Block    -   CSI-RS: Channel State Information Reference Signal    -   PDCCH: Physical Downlink Control Channel    -   PDSCH: Physical Downlink Shared Channel    -   RRC: Radio Resource Control    -   RRM: Radio Resource Management    -   CORESET: Control Resource Set    -   TCI: Transmission Configuration Indicator    -   DCI: Downlink Control Indicator

Terms

The following is a glossary of terms used in this disclosure:

Memory Medium—Any of various types of non-transitory memory devices orstorage devices. The term “memory medium” is intended to include aninstallation medium, e.g., a CD-ROM, floppy disks, or tape device; acomputer system memory or random access memory such as DRAM, DDR RAM,SRAM, EDO RAM, Rambus RAM, etc.; a non-volatile memory such as a Flash,magnetic media, e.g., a hard drive, or optical storage; registers, orother similar types of memory elements, etc. The memory medium mayinclude other types of non-transitory memory as well or combinationsthereof. In addition, the memory medium may be located in a firstcomputer system in which the programs are executed, or may be located ina second different computer system which connects to the first computersystem over a network, such as the Internet. In the latter instance, thesecond computer system may provide program instructions to the firstcomputer for execution. The term “memory medium” may include two or morememory mediums which may reside in different locations, e.g., indifferent computer systems that are connected over a network. The memorymedium may store program instructions (e.g., embodied as computerprograms) that may be executed by one or more processors.

Carrier Medium—a memory medium as described above, as well as a physicaltransmission medium, such as a bus, network, and/or other physicaltransmission medium that conveys signals such as electrical,electromagnetic, or digital signals.

Programmable Hardware Element—includes various hardware devicescomprising multiple programmable function blocks connected via aprogrammable interconnect. Examples include FPGAs (Field ProgrammableGate Arrays), PLDs (Programmable Logic Devices), FPOAs (FieldProgrammable Object Arrays), and CPLDs (Complex PLDs). The programmablefunction blocks may range from fine grained (combinatorial logic or lookup tables) to coarse grained (arithmetic logic units or processorcores). A programmable hardware element may also be referred to as“reconfigurable logic”.

Computer System (or Computer)—any of various types of computing orprocessing systems, including a personal computer system (PC), mainframecomputer system, workstation, network appliance, Internet appliance,personal digital assistant (PDA), television system, grid computingsystem, or other device or combinations of devices. In general, the term“computer system” can be broadly defined to encompass any device (orcombination of devices) having at least one processor that executesinstructions from a memory medium.

User Equipment (UE) (or “UE Device”)—any of various types of computersystems devices which are mobile or portable and which performs wirelesscommunications. Examples of UE devices include mobile telephones orsmart phones (e.g., iPhone™, Android™-based phones), portable gamingdevices (e.g., Nintendo DS™, PlayStation Portable™, Gameboy Advance™,iPhone™), laptops, wearable devices (e.g. smart watch, smart glasses),PDAs, portable Internet devices, music players, data storage devices,other handheld devices, unmanned aerial vehicles (UAVs) (e.g., drones),UAV controllers (UACs), and so forth. In general, the term “UE” or “UEdevice” can be broadly defined to encompass any electronic, computing,and/or telecommunications device (or combination of devices) which iseasily transported by a user and capable of wireless communication.

Base Station—The term “Base Station” has the full breadth of itsordinary meaning, and at least includes a wireless communication stationinstalled at a fixed location and used to communicate as part of awireless telephone system or radio system.

Processing Element (or Processor)—refers to various elements orcombinations of elements that are capable of performing a function in adevice, such as a user equipment or a cellular network device.Processing elements may include, for example: processors and associatedmemory, portions or circuits of individual processor cores, entireprocessor cores, processor arrays, circuits such as an ASIC (ApplicationSpecific Integrated Circuit), programmable hardware elements such as afield programmable gate array (FPGA), as well any of variouscombinations of the above.

Channel—a medium used to convey information from a sender (transmitter)to a receiver. It should be noted that since characteristics of the term“channel” may differ according to different wireless protocols, the term“channel” as used herein may be considered as being used in a mannerthat is consistent with the standard of the type of device withreference to which the term is used. In some standards, channel widthsmay be variable (e.g., depending on device capability, band conditions,etc.). For example, LTE may support scalable channel bandwidths from 1.4MHz to 20 MHz. In contrast, WLAN channels may be 22 MHz wide whileBluetooth channels may be 1 Mhz wide. Other protocols and standards mayinclude different definitions of channels. Furthermore, some standardsmay define and use multiple types of channels, e.g., different channelsfor uplink or downlink and/or different channels for different uses suchas data, control information, etc.

Band—The term “band” has the full breadth of its ordinary meaning, andat least includes a section of spectrum (e.g., radio frequency spectrum)in which channels are used or set aside for the same purpose.

Wi-Fi—The term “Wi-Fi” (or WiFi) has the full breadth of its ordinarymeaning, and at least includes a wireless communication network or RATthat is serviced by wireless LAN (WLAN) access points and which providesconnectivity through these access points to the Internet. Most modernWi-Fi networks (or WLAN networks) are based on IEEE 802.11 standards andare marketed under the name “Wi-Fi”. A Wi-Fi (WLAN) network is differentfrom a cellular network.

3GPP Access—refers to accesses (e.g., radio access technologies) thatare specified by 3GPP standards. These accesses include, but are notlimited to, GSM/GPRS, LTE, LTE-A, and/or 5G NR. In general, 3GPP accessrefers to various types of cellular access technologies.

Non-3GPP Access—refers any accesses (e.g., radio access technologies)that are not specified by 3GPP standards. These accesses include, butare not limited to, WiMAX, CDMA2000, Wi-Fi, WLAN, and/or fixed networks.Non-3GPP accesses may be split into two categories, “trusted” and“untrusted”: Trusted non-3GPP accesses can interact directly with anevolved packet core (EPC) and/or a 5G core (5GC) whereas untrustednon-3GPP accesses interwork with the EPC/5GC via a network entity, suchas an Evolved Packet Data Gateway and/or a 5G NR gateway. In general,non-3GPP access refers to various types on non-cellular accesstechnologies.

Automatically—refers to an action or operation performed by a computersystem (e.g., software executed by the computer system) or device (e.g.,circuitry, programmable hardware elements, ASICs, etc.), without userinput directly specifying or performing the action or operation. Thus,the term “automatically” is in contrast to an operation being manuallyperformed or specified by the user, where the user provides input todirectly perform the operation. An automatic procedure may be initiatedby input provided by the user, but the subsequent actions that areperformed “automatically” are not specified by the user, i.e., are notperformed “manually”, where the user specifies each action to perform.For example, a user filling out an electronic form by selecting eachfield and providing input specifying information (e.g., by typinginformation, selecting check boxes, radio selections, etc.) is fillingout the form manually, even though the computer system must update theform in response to the user actions. The form may be automaticallyfilled out by the computer system where the computer system (e.g.,software executing on the computer system) analyzes the fields of theform and fills in the form without any user input specifying the answersto the fields. As indicated above, the user may invoke the automaticfilling of the form, but is not involved in the actual filling of theform (e.g., the user is not manually specifying answers to fields butrather they are being automatically completed). The presentspecification provides various examples of operations beingautomatically performed in response to actions the user has taken.

Approximately—refers to a value that is almost correct or exact. Forexample, approximately may refer to a value that is within 1 to 10percent of the exact (or desired) value. It should be noted, however,that the actual threshold value (or tolerance) may be applicationdependent. For example, in some embodiments, “approximately” may meanwithin 0.1% of some specified or desired value, while in various otherembodiments, the threshold may be, for example, 2%, 3%, 5%, and soforth, as desired or as required by the particular application.

Concurrent—refers to parallel execution or performance, where tasks,processes, or programs are performed in an at least partiallyoverlapping manner. For example, concurrency may be implemented using“strong” or strict parallelism, where tasks are performed (at leastpartially) in parallel on respective computational elements, or using“weak parallelism”, where the tasks are performed in an interleavedmanner, e.g., by time multiplexing of execution threads.

Various components may be described as “configured to” perform a task ortasks. In such contexts, “configured to” is a broad recitation generallymeaning “having structure that” performs the task or tasks duringoperation. As such, the component can be configured to perform the taskeven when the component is not currently performing that task (e.g., aset of electrical conductors may be configured to electrically connect amodule to another module, even when the two modules are not connected).In some contexts, “configured to” may be a broad recitation of structuregenerally meaning “having circuitry that” performs the task or tasksduring operation. As such, the component can be configured to performthe task even when the component is not currently on. In general, thecircuitry that forms the structure corresponding to “configured to” mayinclude hardware circuits.

Various components may be described as performing a task or tasks, forconvenience in the description. Such descriptions should be interpretedas including the phrase “configured to.” Reciting a component that isconfigured to perform one or more tasks is expressly intended not toinvoke 35 U.S.C. § 112(f) interpretation for that component.

FIGS. 1A and 1B: Communication Systems

FIG. 1A illustrates a simplified example wireless communication system,according to some embodiments. It is noted that the system of FIG. 1A ismerely one example of a possible system, and that features of thisdisclosure may be implemented in any of various systems, as desired.

As shown, the example wireless communication system includes a basestation 102A which communicates over a transmission medium with one ormore user devices 106A, 106B, etc., through 106N. Each of the userdevices may be referred to herein as a “user equipment” (UE). Thus, theuser devices 106 are referred to as UEs or UE devices.

The base station (BS) 102A may be a base transceiver station (BTS) orcell site (a “cellular base station”) and may include hardware thatenables wireless communication with the UEs 106A through 106N.

The communication area (or coverage area) of the base station may bereferred to as a “cell.” The base station 102A and the UEs 106 may beconfigured to communicate over the transmission medium using any ofvarious radio access technologies (RATs), also referred to as wirelesscommunication technologies, or telecommunication standards, such as GSM,UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces),LTE, LTE-Advanced (LTE-A), 5G new radio (5G NR), HSPA, 3GPP2 CDMA2000(e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc. Note that if the base station102A is implemented in the context of LTE, it may alternately bereferred to as an ‘eNodeB’ or ‘eNB’. Note that if the base station 102Ais implemented in the context of 5G NR, it may alternately be referredto as ‘gNodeB’ or ‘gNB’.

As shown, the base station 102A may also be equipped to communicate witha network 100 (e.g., a core network of a cellular service provider, atelecommunication network such as a public switched telephone network(PSTN), and/or the Internet, among various possibilities). Thus, thebase station 102A may facilitate communication between the user devicesand/or between the user devices and the network 100. In particular, thecellular base station 102A may provide UEs 106 with varioustelecommunication capabilities, such as voice, SMS and/or data services.

Base station 102A and other similar base stations (such as base stations102B . . . 102N) operating according to the same or a different cellularcommunication standard may thus be provided as a network of cells, whichmay provide continuous or nearly continuous overlapping service to UEs106A-N and similar devices over a geographic area via one or morecellular communication standards.

Thus, while base station 102A may act as a “serving cell” for UEs 106A-Nas illustrated in FIG. 1 , each UE 106 may also be capable of receivingsignals from (and possibly within communication range of) one or moreother cells (which might be provided by base stations 102B-N and/or anyother base stations), which may be referred to as “neighboring cells”.Such cells may also be capable of facilitating communication betweenuser devices and/or between user devices and the network 100. Such cellsmay include “macro” cells, “micro” cells, “pico” cells, and/or cellswhich provide any of various other granularities of service area size.For example, base stations 102A-B illustrated in FIG. 1 might be macrocells, while base station 102N might be a micro cell. Otherconfigurations are also possible.

In some embodiments, base station 102A may be a next generation basestation, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In someembodiments, a gNB may be connected to a legacy evolved packet core(EPC) network and/or to a NR core (NRC) network. In addition, a gNB cellmay include one or more transition and reception points (TRPs). Inaddition, a UE capable of operating according to 5G NR may be connectedto one or more TRPs within one or more gNBs.

Note that a UE 106 may be capable of communicating using multiplewireless communication standards. For example, the UE 106 may beconfigured to communicate using a wireless networking (e.g., Wi-Fi)and/or peer-to-peer wireless communication protocol (e.g., Bluetooth,Wi-Fi peer-to-peer, etc.) in addition to at least one cellularcommunication protocol (e.g., GSM, UMTS (associated with, for example,WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc.). The UE 106 may alsoor alternatively be configured to communicate using one or more globalnavigational satellite systems (GNSS, e.g., GPS or GLONASS), one or moremobile television broadcasting standards (e.g., ATSC-M/H or DVB-H),and/or any other wireless communication protocol, if desired. Othercombinations of wireless communication standards (including more thantwo wireless communication standards) are also possible.

FIG. 1B illustrates user equipment 106 (e.g., one of the devices 106Athrough 106N) in communication with a base station 102 and an accesspoint 112, according to some embodiments. The UE 106 may be a devicewith both cellular communication capability and non-cellularcommunication capability (e.g., Bluetooth, Wi-Fi, and so forth) such asa mobile phone, a hand-held device, a computer or a tablet, or virtuallyany type of wireless device.

The UE 106 may include a processor that is configured to execute programinstructions stored in memory. The UE 106 may perform any of the methodembodiments described herein by executing such stored instructions.Alternatively, or in addition, the UE 106 may include a programmablehardware element such as an FPGA (field-programmable gate array) that isconfigured to perform any of the method embodiments described herein, orany portion of any of the method embodiments described herein.

The UE 106 may include one or more antennas for communicating using oneor more wireless communication protocols or technologies. In someembodiments, the UE 106 may be configured to communicate using, forexample, CDMA2000 (1xRTT/1xEV-DO/HRPD/eHRPD), LTE/LTE-Advanced, or 5G NRusing a single shared radio and/or GSM, LTE, LTE-Advanced, or 5G NRusing the single shared radio. The shared radio may couple to a singleantenna, or may couple to multiple antennas (e.g., for MIMO) forperforming wireless communications. In general, a radio may include anycombination of a baseband processor, analog RF signal processingcircuitry (e.g., including filters, mixers, oscillators, amplifiers,etc.), or digital processing circuitry (e.g., for digital modulation aswell as other digital processing). Similarly, the radio may implementone or more receive and transmit chains using the aforementionedhardware. For example, the UE 106 may share one or more parts of areceive and/or transmit chain between multiple wireless communicationtechnologies, such as those discussed above.

In some embodiments, the UE 106 may include separate transmit and/orreceive chains (e.g., including separate antennas and other radiocomponents) for each wireless communication protocol with which it isconfigured to communicate. As a further possibility, the UE 106 mayinclude one or more radios which are shared between multiple wirelesscommunication protocols, and one or more radios which are usedexclusively by a single wireless communication protocol. For example,the UE 106 might include a shared radio for communicating using eitherof LTE or 5G NR (or LTE or 1xRTT or LTE or GSM), and separate radios forcommunicating using each of Wi-Fi and Bluetooth. Other configurationsare also possible.

FIG. 2: Access Point Block Diagram

FIG. 2 illustrates an exemplary block diagram of an access point (AP)112. It is noted that the block diagram of the AP of FIG. 2 is only oneexample of a possible system. As shown, the AP 112 may includeprocessor(s) 204 which may execute program instructions for the AP 112.The processor(s) 204 may also be coupled (directly or indirectly) tomemory management unit (MMU) 240, which may be configured to receiveaddresses from the processor(s) 204 and to translate those addresses tolocations in memory (e.g., memory 260 and read only memory (ROM) 250) orto other circuits or devices.

The AP 112 may include at least one network port 270. The network port270 may be configured to couple to a wired network and provide aplurality of devices, such as UEs 106, access to the Internet. Forexample, the network port 270 (or an additional network port) may beconfigured to couple to a local network, such as a home network or anenterprise network. For example, port 270 may be an Ethernet port. Thelocal network may provide connectivity to additional networks, such asthe Internet.

The AP 112 may include at least one antenna 234, which may be configuredto operate as a wireless transceiver and may be further configured tocommunicate with UE 106 via wireless communication circuitry 230. Theantenna 234 communicates with the wireless communication circuitry 230via communication chain 232. Communication chain 232 may include one ormore receive chains, one or more transmit chains or both. The wirelesscommunication circuitry 230 may be configured to communicate via Wi-Fior WLAN, e.g., 802.11. The wireless communication circuitry 230 mayalso, or alternatively, be configured to communicate via various otherwireless communication technologies, including, but not limited to, 5GNR, Long-Term Evolution (LTE), LTE Advanced (LTE-A), Global System forMobile (GSM), Wideband Code Division Multiple Access (WCDMA), CDMA2000,etc., for example when the AP is co-located with a base station in caseof a small cell, or in other instances when it may be desirable for theAP 112 to communicate via various different wireless communicationtechnologies.

In some embodiments, as further described below, an AP 112 may beconfigured to perform methods for cancellation and/or replacement ofphysical uplink shared channels (PUSCHs) with differing priorities,e.g., for ultra-reliable low-latency communication (URLLC) and/orenhanced URLLC (eURLLC) as further described herein.

FIG. 3: Block Diagram of a Base Station

FIG. 3 illustrates an example block diagram of a base station 102,according to some embodiments. It is noted that the base station of FIG.3 is merely one example of a possible base station. As shown, the basestation 102 may include processor(s) 404 which may execute programinstructions for the base station 102. The processor(s) 404 may also becoupled to memory management unit (MMU) 440, which may be configured toreceive addresses from the processor(s) 404 and translate thoseaddresses to locations in memory (e.g., memory 460 and read only memory(ROM) 450) or to other circuits or devices.

The base station 102 may include at least one network port 470. Thenetwork port 470 may be configured to couple to a telephone network andprovide a plurality of devices, such as UE devices 106, access to thetelephone network as described above in FIGS. 1 and 2 .

The network port 470 (or an additional network port) may also oralternatively be configured to couple to a cellular network, e.g., acore network of a cellular service provider. The core network mayprovide mobility related services and/or other services to a pluralityof devices, such as UE devices 106. In some cases, the network port 470may couple to a telephone network via the core network, and/or the corenetwork may provide a telephone network (e.g., among other UE devicesserviced by the cellular service provider).

In some embodiments, base station 102 may be a next generation basestation, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In suchembodiments, base station 102 may be connected to a legacy evolvedpacket core (EPC) network and/or to a NR core (NRC) network. Inaddition, base station 102 may be considered a 5G NR cell and mayinclude one or more transition and reception points (TRPs). In addition,a UE capable of operating according to 5G NR may be connected to one ormore TRPs within one or more gNBs.

The base station 102 may include at least one antenna 434, and possiblymultiple antennas. The at least one antenna 434 may be configured tooperate as a wireless transceiver and may be further configured tocommunicate with UE devices 106 via radio 430. The antenna 434communicates with the radio 430 via communication chain 432.Communication chain 432 may be a receive chain, a transmit chain orboth. The radio 430 may be configured to communicate via variouswireless communication standards, including, but not limited to, 5G NR,LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

The base station 102 may be configured to communicate wirelessly usingmultiple wireless communication standards. In some instances, the basestation 102 may include multiple radios, which may enable the basestation 102 to communicate according to multiple wireless communicationtechnologies. For example, as one possibility, the base station 102 mayinclude an LTE radio for performing communication according to LTE aswell as a 5G NR radio for performing communication according to 5G NR.In such a case, the base station 102 may be capable of operating as bothan LTE base station and a 5G NR base station. As another possibility,the base station 102 may include a multi-mode radio which is capable ofperforming communications according to any of multiple wirelesscommunication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTEand UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

As described further subsequently herein, the BS 102 may includehardware and software components for implementing or supportingimplementation of features described herein. The processor 404 of thebase station 102 may be configured to implement or supportimplementation of part or all of the methods described herein, e.g., byexecuting program instructions stored on a memory medium (e.g., anon-transitory computer-readable memory medium). Alternatively, theprocessor 404 may be configured as a programmable hardware element, suchas an FPGA (Field Programmable Gate Array), or as an ASIC (ApplicationSpecific Integrated Circuit), or a combination thereof. Alternatively(or in addition) the processor 404 of the BS 102, in conjunction withone or more of the other components 430, 432, 434, 440, 450, 460, 470may be configured to implement or support implementation of part or allof the features described herein.

In addition, as described herein, processor(s) 404 may be comprised ofone or more processing elements. In other words, one or more processingelements may be included in processor(s) 404. Thus, processor(s) 404 mayinclude one or more integrated circuits (ICs) that are configured toperform the functions of processor(s) 404. In addition, each integratedcircuit may include circuitry (e.g., first circuitry, second circuitry,etc.) configured to perform the functions of processor(s) 404.

Further, as described herein, radio 430 may be comprised of one or moreprocessing elements. In other words, one or more processing elements maybe included in radio 430. Thus, radio 430 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof radio 430. In addition, each integrated circuit may include circuitry(e.g., first circuitry, second circuitry, etc.) configured to performthe functions of radio 430.

FIG. 4: Block Diagram of a Server

FIG. 4 illustrates an example block diagram of a server 104, accordingto some embodiments. It is noted that the base station of FIG. 4 ismerely one example of a possible server. As shown, the server 104 mayinclude processor(s) 444 which may execute program instructions for theserver 104. The processor(s) 444 may also be coupled to memorymanagement unit (MMU) 474, which may be configured to receive addressesfrom the processor(s) 444 and translate those addresses to locations inmemory (e.g., memory 464 and read only memory (ROM) 454) or to othercircuits or devices.

The server 104 may be configured to provide a plurality of devices, suchas base station 102, UE devices 106, and/or UTM 108, access to networkfunctions, e.g., as further described herein.

In some embodiments, the server 104 may be part of a radio accessnetwork, such as a 5G New Radio (5G NR) radio access network. In someembodiments, the server 104 may be connected to a legacy evolved packetcore (EPC) network and/or to a NR core (NRC) network.

As described further subsequently herein, the server 104 may includehardware and software components for implementing or supportingimplementation of features described herein. The processor 444 of theserver 104 may be configured to implement or support implementation ofpart or all of the methods described herein, e.g., by executing programinstructions stored on a memory medium (e.g., a non-transitorycomputer-readable memory medium). Alternatively, the processor 444 maybe configured as a programmable hardware element, such as an FPGA (FieldProgrammable Gate Array), or as an ASIC (Application Specific IntegratedCircuit), or a combination thereof. Alternatively (or in addition) theprocessor 444 of the server 104, in conjunction with one or more of theother components 454, 464, and/or 474 may be configured to implement orsupport implementation of part or all of the features described herein.

In addition, as described herein, processor(s) 444 may be comprised ofone or more processing elements. In other words, one or more processingelements may be included in processor(s) 444. Thus, processor(s) 444 mayinclude one or more integrated circuits (ICs) that are configured toperform the functions of processor(s) 444. In addition, each integratedcircuit may include circuitry (e.g., first circuitry, second circuitry,etc.) configured to perform the functions of processor(s) 444.

FIG. 5A: Block Diagram of a UE

FIG. 5A illustrates an example simplified block diagram of acommunication device 106, according to some embodiments. It is notedthat the block diagram of the communication device of FIG. 5A is onlyone example of a possible communication device. According toembodiments, communication device 106 may be a user equipment (UE)device, a mobile device or mobile station, a wireless device or wirelessstation, a desktop computer or computing device, a mobile computingdevice (e.g., a laptop, notebook, or portable computing device), atablet, an unmanned aerial vehicle (UAV), a UAV controller (UAC) and/ora combination of devices, among other devices. As shown, thecommunication device 106 may include a set of components 300 configuredto perform core functions. For example, this set of components may beimplemented as a system on chip (SOC), which may include portions forvarious purposes. Alternatively, this set of components 300 may beimplemented as separate components or groups of components for thevarious purposes. The set of components 300 may be coupled (e.g.,communicatively; directly or indirectly) to various other circuits ofthe communication device 106.

For example, the communication device 106 may include various types ofmemory (e.g., including NAND flash 310), an input/output interface suchas connector OF 320 (e.g., for connecting to a computer system; dock;charging station; input devices, such as a microphone, camera, keyboard;output devices, such as speakers; etc.), the display 360, which may beintegrated with or external to the communication device 106, andcellular communication circuitry 330 such as for 5G NR, LTE, GSM, etc.,and short to medium range wireless communication circuitry 329 (e.g.,Bluetooth™ and WLAN circuitry). In some embodiments, communicationdevice 106 may include wired communication circuitry (not shown), suchas a network interface card, e.g., for Ethernet.

The cellular communication circuitry 330 may couple (e.g.,communicatively; directly or indirectly) to one or more antennas, suchas antennas 335 and 336 as shown. The short to medium range wirelesscommunication circuitry 329 may also couple (e.g., communicatively;directly or indirectly) to one or more antennas, such as antennas 337and 338 as shown. Alternatively, the short to medium range wirelesscommunication circuitry 329 may couple (e.g., communicatively; directlyor indirectly) to the antennas 335 and 336 in addition to, or insteadof, coupling (e.g., communicatively; directly or indirectly) to theantennas 337 and 338. The short to medium range wireless communicationcircuitry 329 and/or cellular communication circuitry 330 may includemultiple receive chains and/or multiple transmit chains for receivingand/or transmitting multiple spatial streams, such as in amultiple-input multiple output (MIMO) configuration.

In some embodiments, as further described below, cellular communicationcircuitry 330 may include dedicated receive chains (including and/orcoupled to, e.g., communicatively; directly or indirectly. dedicatedprocessors and/or radios) for multiple RATs (e.g., a first receive chainfor LTE and a second receive chain for 5G NR). In addition, in someembodiments, cellular communication circuitry 330 may include a singletransmit chain that may be switched between radios dedicated to specificRATs. For example, a first radio may be dedicated to a first RAT, e.g.,LTE, and may be in communication with a dedicated receive chain and atransmit chain shared with an additional radio, e.g., a second radiothat may be dedicated to a second RAT, e.g., 5G NR, and may be incommunication with a dedicated receive chain and the shared transmitchain.

The communication device 106 may also include and/or be configured foruse with one or more user interface elements. The user interfaceelements may include any of various elements, such as display 360 (whichmay be a touchscreen display), a keyboard (which may be a discretekeyboard or may be implemented as part of a touchscreen display), amouse, a microphone and/or speakers, one or more cameras, one or morebuttons, and/or any of various other elements capable of providinginformation to a user and/or receiving or interpreting user input.

The communication device 106 may further include one or more smart cards345 that include SIM (Subscriber Identity Module) functionality, such asone or more UICC(s) (Universal Integrated Circuit Card(s)) cards 345.Note that the term “SIM” or “SIM entity” is intended to include any ofvarious types of SIM implementations or SIM functionality, such as theone or more UICC(s) cards 345, one or more eUICCs, one or more eSIMs,either removable or embedded, etc. In some embodiments, the UE 106 mayinclude at least two SIMs. Each SIM may execute one or more SIMapplications and/or otherwise implement SIM functionality. Thus, eachSIM may be a single smart card that may be embedded, e.g., may besoldered onto a circuit board in the UE 106, or each SIM 310 may beimplemented as a removable smart card. Thus the SIM(s) may be one ormore removable smart cards (such as UICC cards, which are sometimesreferred to as “SIM cards”), and/or the SIMs 310 may be one or moreembedded cards (such as embedded UICCs (eUICCs), which are sometimesreferred to as “eSIMs” or “eSIM cards”). In some embodiments (such aswhen the SIM(s) include an eUICC), one or more of the SIM(s) mayimplement embedded SIM (eSIM) functionality; in such an embodiment, asingle one of the SIM(s) may execute multiple SIM applications. Each ofthe SIMs may include components such as a processor and/or a memory;instructions for performing SIM/eSIM functionality may be stored in thememory and executed by the processor. In some embodiments, the UE 106may include a combination of removable smart cards andfixed/non-removable smart cards (such as one or more eUICC cards thatimplement eSIM functionality), as desired. For example, the UE 106 maycomprise two embedded SIMs, two removable SIMs, or a combination of oneembedded SIMs and one removable SIMs. Various other SIM configurationsare also contemplated.

As noted above, in some embodiments, the UE 106 may include two or moreSIMs. The inclusion of two or more SIMs in the UE 106 may allow the UE106 to support two different telephone numbers and may allow the UE 106to communicate on corresponding two or more respective networks. Forexample, a first SIM may support a first RAT such as LTE, and a secondSIM 310 support a second RAT such as 5G NR. Other implementations andRATs are of course possible. In some embodiments, when the UE 106comprises two SIMs, the UE 106 may support Dual SIM Dual Active (DSDA)functionality. The DSDA functionality may allow the UE 106 to besimultaneously connected to two networks (and use two different RATs) atthe same time, or to simultaneously maintain two connections supportedby two different SIMs using the same or different RATs on the same ordifferent networks. The DSDA functionality may also allow the UE 106 tosimultaneously receive voice calls or data traffic on either phonenumber. In certain embodiments the voice call may be a packet switchedcommunication. In other words, the voice call may be received usingvoice over LTE (VoLTE) technology and/or voice over NR (VoNR)technology. In some embodiments, the UE 106 may support Dual SIM DualStandby (DSDS) functionality. The DSDS functionality may allow either ofthe two SIMs in the UE 106 to be on standby waiting for a voice calland/or data connection. In DSDS, when a call/data is established on oneSIM, the other SIM is no longer active. In some embodiments, DSDxfunctionality (either DSDA or DSDS functionality) may be implementedwith a single SIM (e.g., a eUICC) that executes multiple SIMapplications for different carriers and/or RATs.

As shown, the SOC 300 may include processor(s) 302, which may executeprogram instructions for the communication device 106 and displaycircuitry 304, which may perform graphics processing and provide displaysignals to the display 360. The processor(s) 302 may also be coupled tomemory management unit (MMU) 340, which may be configured to receiveaddresses from the processor(s) 302 and translate those addresses tolocations in memory (e.g., memory 306, read only memory (ROM) 350, NANDflash memory 310) and/or to other circuits or devices, such as thedisplay circuitry 304, short to medium range wireless communicationcircuitry 329, cellular communication circuitry 330, connector OF 320,and/or display 360. The MMU 340 may be configured to perform memoryprotection and page table translation or set up. In some embodiments,the MMU 340 may be included as a portion of the processor(s) 302.

As noted above, the communication device 106 may be configured tocommunicate using wireless and/or wired communication circuitry. Thecommunication device 106 may be configured to perform methods forcancellation and/or replacement of physical uplink shared channels(PUSCHs) with differing priorities, e.g., for ultra-reliable low-latencycommunication (URLLC) and/or enhanced URLLC (eURLLC) as furtherdescribed herein.

As described herein, the communication device 106 may include hardwareand software components for implementing the above features for acommunication device 106 to communicate a scheduling profile for powersavings to a network. The processor 302 of the communication device 106may be configured to implement part or all of the features describedherein, e.g., by executing program instructions stored on a memorymedium (e.g., a non-transitory computer-readable memory medium).Alternatively (or in addition), processor 302 may be configured as aprogrammable hardware element, such as an FPGA (Field Programmable GateArray), or as an ASIC (Application Specific Integrated Circuit).Alternatively (or in addition) the processor 302 of the communicationdevice 106, in conjunction with one or more of the other components 300,304, 306, 310, 320, 329, 330, 340, 345, 350, 360 may be configured toimplement part or all of the features described herein.

In addition, as described herein, processor 302 may include one or moreprocessing elements. Thus, processor 302 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof processor 302. In addition, each integrated circuit may includecircuitry (e.g., first circuitry, second circuitry, etc.) configured toperform the functions of processor(s) 302.

Further, as described herein, cellular communication circuitry 330 andshort to medium range wireless communication circuitry 329 may eachinclude one or more processing elements. In other words, one or moreprocessing elements may be included in cellular communication circuitry330 and, similarly, one or more processing elements may be included inshort to medium range wireless communication circuitry 329. Thus,cellular communication circuitry 330 may include one or more integratedcircuits (ICs) that are configured to perform the functions of cellularcommunication circuitry 330. In addition, each integrated circuit mayinclude circuitry (e.g., first circuitry, second circuitry, etc.)configured to perform the functions of cellular communication circuitry330. Similarly, the short to medium range wireless communicationcircuitry 329 may include one or more ICs that are configured to performthe functions of short to medium range wireless communication circuitry329. In addition, each integrated circuit may include circuitry (e.g.,first circuitry, second circuitry, etc.) configured to perform thefunctions of short to medium range wireless communication circuitry 329.

FIG. 5B: Block Diagram of Cellular Communication Circuitry

FIG. 5B illustrates an example simplified block diagram of cellularcommunication circuitry, according to some embodiments. It is noted thatthe block diagram of the cellular communication circuitry of FIG. 5B isonly one example of a possible cellular communication circuit. Accordingto embodiments, cellular communication circuitry 330 may be included ina communication device, such as communication device 106 describedabove. As noted above, communication device 106 may be a user equipment(UE) device, a mobile device or mobile station, a wireless device orwireless station, a desktop computer or computing device, a mobilecomputing device (e.g., a laptop, notebook, or portable computingdevice), a tablet and/or a combination of devices, among other devices.

The cellular communication circuitry 330 may couple (e.g.,communicatively; directly or indirectly) to one or more antennas, suchas antennas 335 a-b and 336 as shown (in FIG. 3 ). In some embodiments,cellular communication circuitry 330 may include dedicated receivechains (including and/or coupled to, e.g., communicatively; directly orindirectly. dedicated processors and/or radios) for multiple RATs (e.g.,a first receive chain for LTE and a second receive chain for 5G NR). Forexample, as shown in FIG. 5 , cellular communication circuitry 330 mayinclude a modem 510 and a modem 520. Modem 510 may be configured forcommunications according to a first RAT, e.g., such as LTE or LTE-A, andmodem 520 may be configured for communications according to a secondRAT, e.g., such as 5G NR.

As shown, modem 510 may include one or more processors 512 and a memory516 in communication with processors 512. Modem 510 may be incommunication with a radio frequency (RF) front end 530. RF front end530 may include circuitry for transmitting and receiving radio signals.For example, RF front end 530 may include receive circuitry (RX) 532 andtransmit circuitry (TX) 534. In some embodiments, receive circuitry 532may be in communication with downlink (DL) front end 550, which mayinclude circuitry for receiving radio signals via antenna 335 a.

Similarly, modem 520 may include one or more processors 522 and a memory526 in communication with processors 522. Modem 520 may be incommunication with an RF front end 540. RF front end 540 may includecircuitry for transmitting and receiving radio signals. For example, RFfront end 540 may include receive circuitry 542 and transmit circuitry544. In some embodiments, receive circuitry 542 may be in communicationwith DL front end 560, which may include circuitry for receiving radiosignals via antenna 335 b.

In some embodiments, a switch 570 may couple transmit circuitry 534 touplink (UL) front end 572. In addition, switch 570 may couple transmitcircuitry 544 to UL front end 572. UL front end 572 may includecircuitry for transmitting radio signals via antenna 336. Thus, whencellular communication circuitry 330 receives instructions to transmitaccording to the first RAT (e.g., as supported via modem 510), switch570 may be switched to a first state that allows modem 510 to transmitsignals according to the first RAT (e.g., via a transmit chain thatincludes transmit circuitry 534 and UL front end 572). Similarly, whencellular communication circuitry 330 receives instructions to transmitaccording to the second RAT (e.g., as supported via modem 520), switch570 may be switched to a second state that allows modem 520 to transmitsignals according to the second RAT (e.g., via a transmit chain thatincludes transmit circuitry 544 and UL front end 572).

In some embodiments, the cellular communication circuitry 330 may beconfigured to perform methods cancellation and/or replacement ofphysical uplink shared channels (PUSCHs) with differing priorities,e.g., for ultra-reliable low-latency communication (URLLC) and/orenhanced URLLC (eURLLC) as further described herein.

As described herein, the modem 510 may include hardware and softwarecomponents for implementing the above features or for time divisionmultiplexing UL data for NSA NR operations, as well as the various othertechniques described herein. The processors 512 may be configured toimplement part or all of the features described herein, e.g., byexecuting program instructions stored on a memory medium (e.g., anon-transitory computer-readable memory medium). Alternatively (or inaddition), processor 512 may be configured as a programmable hardwareelement, such as an FPGA (Field Programmable Gate Array), or as an ASIC(Application Specific Integrated Circuit). Alternatively (or inaddition) the processor 512, in conjunction with one or more of theother components 530, 532, 534, 550, 570, 572, 335 and 336 may beconfigured to implement part or all of the features described herein.

In addition, as described herein, processors 512 may include one or moreprocessing elements. Thus, processors 512 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof processors 512. In addition, each integrated circuit may includecircuitry (e.g., first circuitry, second circuitry, etc.) configured toperform the functions of processors 512.

As described herein, the modem 520 may include hardware and softwarecomponents for implementing the above features for communicating ascheduling profile for power savings to a network, as well as thevarious other techniques described herein. The processors 522 may beconfigured to implement part or all of the features described herein,e.g., by executing program instructions stored on a memory medium (e.g.,a non-transitory computer-readable memory medium). Alternatively (or inaddition), processor 522 may be configured as a programmable hardwareelement, such as an FPGA (Field Programmable Gate Array), or as an ASIC(Application Specific Integrated Circuit). Alternatively (or inaddition) the processor 522, in conjunction with one or more of theother components 540, 542, 544, 550, 570, 572, 335 and 336 may beconfigured to implement part or all of the features described herein.

In addition, as described herein, processors 522 may include one or moreprocessing elements. Thus, processors 522 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof processors 522. In addition, each integrated circuit may includecircuitry (e.g., first circuitry, second circuitry, etc.) configured toperform the functions of processors 522.

FIGS. 6A and 6B: 5G NR Architecture with LTE

In some implementations, fifth generation (5G) wireless communicationwill initially be deployed concurrently with current wirelesscommunication standards (e.g., LTE). For example, dual connectivitybetween LTE and 5G new radio (5G NR or NR) has been specified as part ofthe initial deployment of NR. Thus, as illustrated in FIGS. 6A-B,evolved packet core (EPC) network 600 may continue to communicate withcurrent LTE base stations (e.g., eNB 602). In addition, eNB 602 may bein communication with a 5G NR base station (e.g., gNB 604) and may passdata between the EPC network 600 and gNB 604. Thus, EPC network 600 maybe used (or reused) and gNB 604 may serve as extra capacity for UEs,e.g., for providing increased downlink throughput to UEs. In otherwords, LTE may be used for control plane signaling and NR may be usedfor user plane signaling. Thus, LTE may be used to establish connectionsto the network and NR may be used for data services.

FIG. 6B illustrates a proposed protocol stack for eNB 602 and gNB 604.As shown, eNB 602 may include a medium access control (MAC) layer 632that interfaces with radio link control (RLC) layers 622 a-b. RLC layer622 a may also interface with packet data convergence protocol (PDCP)layer 612 a and RLC layer 622 b may interface with PDCP layer 612 b.Similar to dual connectivity as specified in LTE-Advanced Release 12,PDCP layer 612 a may interface via a master cell group (MCG) bearer withEPC network 600 whereas PDCP layer 612 b may interface via a splitbearer with EPC network 600.

Additionally, as shown, gNB 604 may include a MAC layer 634 thatinterfaces with RLC layers 624 a-b. RLC layer 624 a may interface withPDCP layer 612 b of eNB 602 via an X₂ interface for information exchangeand/or coordination (e.g., scheduling of a UE) between eNB 602 and gNB604. In addition, RLC layer 624 b may interface with PDCP layer 614.Similar to dual connectivity as specified in LTE-Advanced Release 12,PDCP layer 614 may interface with EPC network 600 via a secondary cellgroup (SCG) bearer. Thus, eNB 602 may be considered a master node (MeNB)while gNB 604 may be considered a secondary node (SgNB). In somescenarios, a UE may be required to maintain a connection to both an MeNBand a SgNB. In such scenarios, the MeNB may be used to maintain a radioresource control (RRC) connection to an EPC while the SgNB may be usedfor capacity (e.g., additional downlink and/or uplink throughput).

FIGS. 7A, 7B and 8 : 5G Core Network Architecture—Interworking withWi-Fi

In some embodiments, the 5G core network (CN) may be accessed via (orthrough) a cellular connection/interface (e.g., via a 3GPP communicationarchitecture/protocol) and a non-cellular connection/interface (e.g., anon-3GPP access architecture/protocol such as Wi-Fi connection). FIG. 7Aillustrates an example of a 5G network architecture that incorporatesboth 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access tothe 5G CN, according to some embodiments. As shown, a user equipmentdevice (e.g., such as UE 106) may access the 5G CN through both a radioaccess network (RAN, e.g., such as gNB or base station 604) and anaccess point, such as AP 112. The AP 112 may include a connection to theInternet 700 as well as a connection to a non-3GPP inter-workingfunction (N3IWF) 702 network entity. The N3IWF may include a connectionto a core access and mobility management function (AMF) 704 of the 5GCN. The AMF 704 may include an instance of a 5G mobility management (5GMM) function associated with the UE 106. In addition, the RAN (e.g., gNB604) may also have a connection to the AMF 704. Thus, the 5G CN maysupport unified authentication over both connections as well as allowsimultaneous registration for UE 106 access via both gNB 604 and AP 112.As shown, the AMF 704 may include one or more functional entitiesassociated with the 5G CN (e.g., network slice selection function (NSSF)720, short message service function (SMSF) 722, application function(AF) 724, unified data management (UDM) 726, policy control function(PCF) 728, and/or authentication server function (AUSF) 730). Note thatthese functional entities may also be supported by a session managementfunction (SMF) 706 a and an SMF 706 b of the 5G CN. The AMF 706 may beconnected to (or in communication with) the SMF 706 a. Further, the gNB604 may in communication with (or connected to) a user plane function(UPF) 708 a that may also be communication with the SMF 706 a.Similarly, the N3IWF 702 may be communicating with a UPF 708 b that mayalso be communicating with the SMF 706 b. Both UPFs may be communicatingwith the data network (e.g., DN 710 a and 710 b) and/or the Internet 700and Internet Protocol (IP) Multimedia Subsystem/IP Multimedia CoreNetwork Subsystem (IMS) core network 710.

FIG. 7B illustrates an example of a 5G network architecture thatincorporates both dual 3GPP (e.g., LTE and 5G NR) access and non-3GPPaccess to the 5G CN, according to some embodiments. As shown, a userequipment device (e.g., such as UE 106) may access the 5G CN throughboth a radio access network (RAN, e.g., such as gNB or base station 604or eNB or base station 602) and an access point, such as AP 112. The AP112 may include a connection to the Internet 700 as well as a connectionto the N3IWF 702 network entity. The N3IWF may include a connection tothe AMF 704 of the 5G CN. The AMF 704 may include an instance of the 5GMM function associated with the UE 106. In addition, the RAN (e.g., gNB604) may also have a connection to the AMF 704. Thus, the 5G CN maysupport unified authentication over both connections as well as allowsimultaneous registration for UE 106 access via both gNB 604 and AP 112.In addition, the 5G CN may support dual-registration of the UE on both alegacy network (e.g., LTE via base station 602) and a 5G network (e.g.,via base station 604). As shown, the base station 602 may haveconnections to a mobility management entity (MME) 742 and a servinggateway (SGW) 744. The MME 742 may have connections to both the SGW 744and the AMF 704. In addition, the SGW 744 may have connections to boththe SMF 706 a and the UPF 708 a. As shown, the AMF 704 may include oneor more functional entities associated with the 5G CN (e.g., NSSF 720,SMSF 722, AF 724, UDM 726, PCF 728, and/or AUSF 730). Note that UDM 726may also include a home subscriber server (HSS) function and the PCF mayalso include a policy and charging rules function (PCRF). Note furtherthat these functional entities may also be supported by the SMF706 a andthe SMF 706 b of the 5G CN. The AMF 706 may be connected to (or incommunication with) the SMF 706 a. Further, the gNB 604 may incommunication with (or connected to) the UPF 708 a that may also becommunication with the SMF 706 a. Similarly, the N3IWF 702 may becommunicating with a UPF 708 b that may also be communicating with theSMF 706 b. Both UPFs may be communicating with the data network (e.g.,DN 710 a and 710 b) and/or the Internet 700 and IMS core network 710.

Note that in various embodiments, one or more of the above describednetwork entities may be configured to perform methods to improvesecurity checks in a 5G NR network, including mechanisms cancellationand/or replacement of physical uplink shared channels (PUSCHs) withdiffering priorities, e.g., for ultra-reliable low-latency communication(URLLC) and/or enhanced URLLC (eURLLC), e.g., as further describedherein.

FIG. 8 illustrates an example of a baseband processor architecture for aUE (e.g., such as UE 106), according to some embodiments. The basebandprocessor architecture 800 described in FIG. 8 may be implemented on oneor more radios (e.g., radios 329 and/or 330 described above) or modems(e.g., modems 510 and/or 520) as described above. As shown, thenon-access stratum (NAS) 810 may include a 5G NAS 820 and a legacy NAS850. The legacy NAS 850 may include a communication connection with alegacy access stratum (AS) 870. The 5G NAS 820 may include communicationconnections with both a 5G AS 840 and a non-3GPP AS 830 and Wi-Fi AS832. The 5G NAS 820 may include functional entities associated with bothaccess stratums. Thus, the 5G NAS 820 may include multiple 5G MMentities 826 and 828 and 5G session management (SM) entities 822 and824. The legacy NAS 850 may include functional entities such as shortmessage service (SMS) entity 852, evolved packet system (EPS) sessionmanagement (ESM) entity 854, session management (SM) entity 856, EPSmobility management (EMM) entity 858, and mobility management (MM)/GPRSmobility management (GMM) entity 860. In addition, the legacy AS 870 mayinclude functional entities such as LTE AS 872, UMTS AS 874, and/orGSM/GPRS AS 876.

Thus, the baseband processor architecture 800 allows for a common 5G-NASfor both 5G cellular and non-cellular (e.g., non-3GPP access). Note thatas shown, the 5G MM may maintain individual connection management andregistration management state machines for each connection.Additionally, a device (e.g., UE 106) may register to a single PLMN(e.g., 5G CN) using 5G cellular access as well as non-cellular access.Further, it may be possible for the device to be in a connected state inone access and an idle state in another access and vice versa. Finally,there may be common 5G-MM procedures (e.g., registration,de-registration, identification, authentication, as so forth) for bothaccesses.

Note that in various embodiments, one or more of the above describedfunctional entities of the 5G NAS and/or 5G AS may be configured toperform methods cancellation and/or replacement of physical uplinkshared channels (PUSCHs) with differing priorities, e.g., forultra-reliable low-latency communication (URLLC) and/or enhanced URLLC(eURLLC), e.g., as further described herein.

PUSCH Cancellation and/or Replacement

In current implementations, e.g., such as implementations standardizedby 3GPP Release 15, a physical uplink shared channel (PUSCH) may bescheduled with downlink control information (DCI) on a physical downlinkcontrol channel (PDCCH) and/or through a configured grant (CG). Notethat in various implementations, PUSCH may be used to carry (e.g.,transmit from a UE to a network entity, such as a base station) radioresource control (RRC) signaling messages, uplink control information,and/or application (or user) data. Additionally, there are two types ofconfigured (uplink) grants: type 1 and type 2. For a type 1 CG, RRCsignaling provides a configured uplink grant (including a periodicity)whereas for type 2, RRC signaling defines a periodicity of theconfigured uplink grant while PDCCH addressed to configured schedulingradio network temporary identifier (CS-RNTI) may either signal andactivate the configured uplink grant or deactivate the configured uplinkgrant. In other words; a PDCCH addressed to CS-RNTI may indicate thatthe configured uplink grant may be implicitly reused according to theperiodicity defined by RRC, e.g., until deactivated.

Additionally, in current implementations, e.g., such as implementationsstandardized by 3GPP Release 15, a single slot transmission, with PUSCHmapping type A or PUSCH mapping type B, can be used for a dynamic uplinkgrant or a configured uplink grant. Additionally, a PUSCH with slotaggregation can be used for dynamic uplink grant (DG) and/or configureduplink grant (CG). Hence, for PUSCH with slot aggregation, a transportblock may be used for transmissions in different slots following ahybrid automatic repeat request (HARQ) redundancy version sequence. Thenumber of slots involved in slot aggregation (e.g., aggregation factor)may be configured separately through RRC signaling. Further. for a DGPUSCH, an aggregation factor may be configured for the DG PUSCH throughpusch-AggregationFactor {n2, n4, n8} (e.g., 2 slots, 4 slots, and/or 8slots). Additionally, for a CG PUSCH, an aggregation factor may be

configured through a parameter repK {n1, n2, n4, n8} (e.g., 1 slot, 2slots, 4 slots, or 8 slots). As for HARQ redundancy version sequence forslot aggregation, for CG PUSCH, the HARQ redundancy version sequence mayRRC configured, e.g., repK-RV {s1-0231, s2-0303, s3-0000}. Additionally,the HARQ redundancy version sequence for DG PUSCH may derived froms1-0231 through repetition while a first used redundancy version may bedynamically signaled by a base station in an uplink DCI, e.g., the basestation may signal starting a PUSCH slot aggregation with “3”. Hence, ifa pusch-AggregationFactor is n8, then HARQ redundancy version sequence[3102 3102] may be used for transmission over 8 slots. Note that in 3GPPRelease 15, pusch-AggregationFactor and repK may be RRC configured forboth DG and CG, respectively. Additionally, with PUSCH slot aggregation,while HARQ redundancy versions may be different for transmissions indifferent slots, time-frequency resources occupied by the PUSCH may bethe same across slots.

Further, in current implementations, e.g., such as implementationsstandardized by 3GPP Release 15, higher layer configured parameters repKand repK-RV may define K repetitions to be applied to a transmittedtransport block and a redundancy version pattern to be applied to therepetitions. In addition, if the parameter repK-RV is not provided inthe CG configuration (e.g., via a configuredGrantConfig parameter), aredundancy version for uplink transmissions with a configured grant maybe set to 0. Otherwise, for the nth transmission occasion among Krepetitions, n=1, 2, . . . , K, the redundancy version may be associatedwith (mod(n-1,4)+1)th value in the configured RV sequence. Hence, theinitial transmission of a transport block may start at

-   -   (i) a first transmission occasion of the K repetitions if the        configured RV sequence is {0,2,3,1};    -   (ii) any transmission occasion of the K repetitions that are        associated with RV=0 if the configured RV sequence is 10,3,0,31;        and/or    -   (iii) any transmission occasions of the K repetitions if the        configured RV sequence is {0,0,0,0}, except the last        transmission occasion when K=8.        Note that for any RV sequence, repetitions may be terminated        after transmitting K repetitions and/or at a last transmission        occasion among the K repetitions within a period P and/or from a        starting symbol of the repetition that overlaps with a PUSCH        with the same HARQ process scheduled by DCI format 0_0 or DCI        format 0_1, whichever is reached first. Note further, that the        UE may not be expected to be configured with a time duration for        the transmission of K repetitions larger than a time duration        derived by the periodicity, P. Additionally, if the UE        determines that, for a transmission occasion, the number of        symbols available for the PUSCH transmission in a slot is        smaller than transmission duration L, the UE does not transmit        the PUSCH in the transmission occasion. Note that for both Type        1 and Type 2 PUSCH transmissions with a configured grant, when        the UE is configured with repK>1, the UE may repeat the        transmission block across the repK consecutive slots applying        the same symbol allocation in each slot. In addition, a Type 1        or Type 2 PUSCH transmission with a configured grant in a slot        may be omitted according to conditions as specified in 3GPP TS        38.213.

In addition, in current implementations, e.g., such as implementationsstandardized by 3GPP Release 15, with a configured grant configuration,uplink resources may be available for data transmission from a UE.However, if there is no data in a buffer for configured granttransmission, the UE does not need to transmit over the configuredresources. Thus, it is useful differentiate an actual CG PUSCHtransmission and CG PUSCH transmission occasion. Thus, as CGtransmission is initiated by the UE and a base station may not be awareof a potential CG transmission initiated by the UE, two conditions aredefined concerning DG scheduling timing, e.g., so the UE may have enoughtime to prepare for DG transmission if the DG transmission overlaps withthe CG transmission occasion.

A first condition/restriction regarding DG scheduled over (e.g., timeoverlapping a) CG transmission occasion is that a UE may not be expectedto be scheduled by a physical downlink control channel (PDCCH) ending insymbol i to transmit a physical uplink shared channel (PUSCH) on aserving cell overlapping in time with a transmission occasion, where theUE is allowed to transmit a PUSCH with a configured grant (e.g., asdefined in 3GPP TS 38.321 Release 15), starting in a symbol j on theserving cell if the end of symbol I is not at least N₂ symbols beforethe beginning of symbol j. Note that in such instances, the value of N₂in symbols is determined according to processing capabilities of the UEas defined in 3GPP Release 15. Additionally, in such instances, N₂ andthe symbol duration may be based on a minimum of a subcarrier spacingcorresponding to the PUSCH with the configured grant and a subcarrierspacing of the PDCCH scheduling the PUSCH.

Additionally, a second condition regarding CG is that a UE may not beexpected to be scheduled by a PDCCH ending in symbol i to transmit aPUSCH on a serving cell for a hybrid automatic repeat request (HARQ)process if there is a transmission occasion where the UE is allowed totransmit a PUSCH with a configured grant (e.g., as defined in 3GPP TS38.321 Release 15) with the HARQ process on the serving cell starting ina symbol j occurring after symbol i and if the gap between the end ofthe PDCCH and the beginning of symbol j is less than N₂ symbols. Notethat in such instances, the value of N₂ in symbols is determinedaccording to processing capabilities of the UE as defined in 3GPPRelease 15. Additionally, in such instances, N₂ and the symbol durationmay be based on a minimum of a subcarrier spacing corresponding to thePUSCH with the configured grant and a subcarrier spacing of the PDCCHscheduling the PUSCH.

In the first condition described above, PDCCH scheduling a DG PUSCHwhich overlaps with a CG PUSCH transmission occasion has to come N2symbols prior to the start of the CG PUSCH transmission occasion. Thus,with this first condition, the UE does not need to handle the case wherethe PDCCH scheduling a DG PUSCH comes less than N2 symbols prior to thestart of the CG PUSCH transmission occasion. In the second conditiondescribed above, if a DG PUSCH has the same HARQ process ID as the HARQprocess ID associated with CG PUSCH transmission occasion, no matterwhether the DG PUSCH overlaps with the CG PUSCH transmission occasion ornot, the PDCCH scheduling the DG PUSCH has to come at least N₂ symbolsprior to the start of the CG transmission occasion.

For example, under the first condition described above, three cases maybe defined as illustrated by FIG. 9 . In a first case, in which adynamic grant, e.g., PDCCH for DG PUSCH 920, schedules a transmission tooccur before a configured grant opportunity, then, so long at PUSCH-1922 (e.g., configured by PDCCH for DG PUSCH 920) occurs at least N₂symbols after the dynamic grant, the transmission will be successful, asshown. In a second case, in which a dynamic grant, e.g., PDCCH for DGPUSCH 930, schedules a transmission to occur after a configured grantopportunity, then, even if PUSCH-2 934 occurs at least N₂ symbols afterthe dynamic grant, the transmission will be dropped in favor of aconfigured grant transmission, e.g., CG transmission 932, as shown. In athird case, in which a dynamic grant, e.g., PDCCH for DG PUSCH 940occurs less than N₂ symbols before the configured grant opportunity,then the scheduled transmission PUSCH-2 942 will be dropped as thedynamic grant occurred within N₂ symbols of the configured grantopportunity and is thus, not allowed.

As another example, under the second condition described above, twocases may be defined as illustrated by FIG. 10 . As shown, a first CGconfiguration may be associated with a first HARQ process and a secondCG configuration may be associated with a second HARQ process, thus CGtransmission 1022 may be associated with both the first and second HARQprocesses. In a first case, a dynamic grant, e.g., PDCCH for DG PUSCH1030, schedules a transmission associated with the first HARQ process,e.g., PUSCH-5 1032, to occur at an earliest starting time for a dynamicgrant, however, under the second condition, the transmission will bedropped as not allowed. In a second case, a dynamic grant, e.g., PDCCHfor DG PUSCH 1040, schedules a transmission associated with a third HARQprocess, e.g., PUSCH-6 1042, to occur at an earliest starting time for adynamic grant and, under the second condition, the transmission willoccur as the transmission is not associated with the first or secondHARQ process.

Hence, in current implementations, if a DG grant for PUSCH is sent atleast N₂ symbols before the start of a CG transmission occasion, any DGtransmission (e.g., no restriction on HARQ process ID, no restriction onoverlapping with CG transmission occasion, but at least N₂ symbolsbetween scheduling DCI and DG transmission) may be allowed.Additionally, in current implementations, if a DG grant for PUSCH issent at fewer than N₂ symbols before the start of CG transmissionoccasion, as long as the DG PUSCH starts after the CG transmissionoccasion (note that the case that the DG PUSCH overlaps with the CGtransmission occasion is excluded by the first condition and the casethe DG PUSCH starts prior to the CG transmission occasion is not allowedas its gap to the scheduling DCI would be less than N₂) and the DG PUSCHHARQ process identifier (ID) does not overlap with any of the CGtransmission occasion's HARQ process IDs, then the DG PUSCH may beallowed.

In addition to these conditions, in current implementations, e.g., suchas implementations standardized by 3GPP Release 15, for a DG PUSCHscheduled by a DCI overriding a CG PUSCH configured with repetitionfactor K>1:

-   -   (i) if a HARQ process is the same between the DG and the CG, DG        overrides all remaining repetition occasions after the end of        PDCCH reception, e.g., under a timeline specified in 3GPP TS        38.214 section 6.1;    -   (ii) otherwise, DG overrides only the CG repetition overlapped        with DG, e.g., under a timeline specified in 3GPP TS 38.214        section 6.1.        Further, a DG overriding a CG is supported when the timeline        conditions are satisfied in various instances.

For example, a DG overriding a CG is supported when the timelineconditions are satisfied if the DG has a different HARQ Process ID fromthat of the CG's. Note that in a first scenario, the DG may be a singletransmission and the CG may be a single transmission. In such ascenario, if the CG collides with the DG, then the CG is dropped oroverridden, and the UE may conduct transmission with the DG. Note thatin a second scenario, the DG may be single transmission and the CG maybe with slot aggregation. In such a scenario, if a CG transmission at atransmission occasion collides with the DG, then the CG transmission atthat transmission occasion is dropped or overridden, and the UE mayconduct transmission with the DG. Additionally, for transmissionoccasions not colliding the DG, CG transmissions may be conducted by theUE. Note further that in a third scenario, a DG may be with slotaggregation and the CG may be with slot aggregation. In such a scenario,if a CG transmission at a transmission occasion collides with a DGtransmission, then the CG transmission at that transmission occasion isdropped or overridden, and the UE may conduct transmission with the DGtransmission. Additionally; for CG transmission occasions not collidingwith any DG transmissions, CG transmissions may be conducted by the UE.Further, in a fourth scenario, a DG may be with slot aggregation and theCG may be a single slot transmission.

In addition, a DG overriding a CG is supported when the timelineconditions are satisfied if the DG has the same HARQ Process ID fromthat of the CG's. Note that in a first scenario, the DG is may be asingle transmission and the CG may be a single transmission. In such ascenario, if the CG collides with the DG, then the CG is dropped oroverridden, and the UE may conduct transmission with the DG. In a secondscenario, the DG may be a single transmission and the CG may be withslot aggregation. In such a scenario, if a CG transmission at atransmission occasion collides with the DG, then the CG transmission atthat transmission occasion and subsequent transmission occasions aredropped (or overridden), and the UE may conduct transmission with theDG. In a third scenario, the DG may be with slot aggregation and the CGmay be with slot aggregation.

As a further example, a DG overriding a CG is supported when thetimeline conditions are satisfied if a CG transmission at an occasioncollides with a DG transmission, then the CG transmission at thatoccasion and subsequent occasions are dropped (or overridden), and theUE conducts transmission with the DG transmission.

Additionally, a DG overriding a CG is supported when the timelineconditions are satisfied if the CG transmission at an occasion collideswith a DG transmission, then the CG transmission at that occasion isdropped or overridden, and the UE conducts transmission with the DGtransmission.

FIGS. 12A-C illustrate examples of implementations of configuredgrant/dynamic grant collision handling, according to the aboveconditions. For example, FIG. 12A illustrates an example of a configuredgrant, e.g., CG 1210 a-d, scheduled across multiple slots, e.g., slots nto n+3, colliding with a dynamic grant with a different HARQ process ID,e.g., DG with different HARQ-ID 1212, as compared to the configuredgrant. As shown, based on the above conditions/rules, a UE will dropand/or override the transmission occasion corresponding to the dynamicgrant (e.g., so the UE may transmit the dynamic grant) and transmitduring the remaining configured grant transmission occasions. As anotherexample, FIG. 12B illustrates an example of a configured grant, e.g., CG1210 a-d, scheduled across multiple slots, e.g., slots n to n+3,colliding with a dynamic grant with the same HARQ process ID, e.g., DGwith same HARQ-ID 1222, as compared to the configured grant. As shown,based on the above conditions/rules, a UE will drop and/or override thetransmission occasion corresponding to the dynamic grant (e.g., so theUE may transmit the dynamic grant) and any configured grants occurringafter the dynamic grant and transmit during the remaining configuredgrant transmission occasions. As a further example, FIG. 12C illustratesan example of a configured grant, e.g., CG 1210 a-d, scheduled acrossmultiple slots, e.g., slots n to n+3, colliding with a dynamic grantwith a different HARQ process ID, e.g., DG with different HARQ-ID 1212,as compared to the configured grant and also scheduled across multipleslots. As shown, based on the above conditions/rules, a UE will dropand/or override transmission occasions corresponding to the dynamicgrant (e.g., so the UE may transmit the dynamic grant) and transmitduring the remaining configured grant transmission occasions.

Given the above, 3GPP release 16 standardized enhancements such asintroduction of PUSCH repetition type A and PUSCH repetition type B.According to PUSCH repetition type A, for a dynamic grant PUSCH, arepetition factor (which may be dynamically indicated by a basestation), indicates a number of slots where PUSCH is transmitted. Notethat the main difference between PUSCH repetition type A and PUSCH withslot aggregation, is how the aggregation factor or repetition factor issignaled; for PUSCH repetition type A, it is through dynamic signaling(e.g., an UL DCI), for PUSCH with slot aggregation, it is through RRCsignaling. According to PUSCH repetition type B, a PUSCH transmissionincludes one or more nominal repetition and each nominal repetition canbe segmented into zero, one or more actual repetition(s) if the nominalrepetition would cross a slot boundary, thereby colliding with an OFDMsymbol not for uplink transmission (e.g., from SFI or an invalid symbolpattern). Note that due to collision with symbol(s) not for uplinktransmission and/or crossing a slot boundary, a nominal repetition maynot lead to any actual repetition, e.g., the entire nominal repetitionmay be dropped. Note further that if a nominal repetition has more thanone OFDM symbol, but an actual repetition resulted from the nominalrepetition has a single OFDM symbol, the actual repetition of one symbolmay be dropped. Additionally, PUSCH transmissions with repetition type Bmay be characterized by three parameters, including a starting symbol(S), a number of symbols in a nominal repetition (L), and a number ofnominal repetitions in the PUSCH (K).

In addition to introducing PUSCH repetition types A and B, 3GPP release16 introduced enhancements to configured grants. In particular, for anuplink bandwidth part at an uplink serving cell, up to 12 configuredgrant configurations can be configured ty the network, including bothtype 1 and type 2 configured grants. Thus, there may be 3 types oftransmission schemes to consider, such as single slot transmission,multiple slot transmission, with either PUSCH slot aggregation or PUSCHrepetition type A, and/or PUSCH repetition type B.

Further, 3GPP release 16 introduced a physical layer priorityindication, e.g., to support multiplexing of UCI and PUSCH for differenttraffics, such as enhanced mobile broadband (eMBB), URLLC, and/oreURLLC. In particular, for PUSCH, a configured grant configuration maybe RRC configured with a physical layer priority (low priority, highpriority), hence a configured grant PUSCH transmission can be associatedwith a physical layer priority. Similarly, for dynamic grant PUSCH, apriority indicator field is introduced in DCI format 0_1 and UL DCIformat (0_2), hence a dynamic grant PUSCH can be associated with aphysical layer priority as well.

Additionally, as multiple configured grant configurations are supportedon a bandwidth part (BWP) in 3GPP Release 16, it is not clear as towhether a later configured grant with the same physical layer priorityis allowed to override an earlier configured grant. Further, assumingsuch a UE behavior is supported, base station blind detection couldbecome onerously difficult and essentially the base station receiverwould need to attempt decoding of each possible configured grant. Such ascheme would also be detrimental to system performance and maydiscourage network from utilizing configured grants, which in the end,hurts UE experience.

In addition, due to support of multiple configured grants on a bandwidthpart, nested transmissions may arise, e.g., as illustrated by FIG. 11 .As shown, a UE may be configured with multiple configured grant PUSCHsas well as have a dynamic grant PUSCH. In such instances a UE may needto maintain multiple transport blocks in its layer 1 buffer and blinddetection at the base station may onerously difficult.

These enhancements introduced in 3GPP release 16 may lead to differentUE behavior than discussed above with regards to 3GPP release 15, e.g.,based on PUSCH repetition A and PUSCH repetition type B, in instances ofmultiple configured grant configurations on a bandwidth part, and/or dueto physical layer priority for PUSCH. In addition, with the introductionof physical layer priority for PUSCH, cancellation and replacementbehavior has been pursued as a solution to handle URLLC traffic in theface of ongoing eMBB traffic in order to reduce scheduling/transmissionlatency. Additionally, given the introduction of PUSCH repetition type Aand PUSCH repetition B, the above described conditions/rules associatedwith 3GPP release 15 behavior do not cover all aspects of theenhancements introduced in 3GPP release 16.

Embodiments described herein provide systems, methods, and mechanismsfor cancellation and/or replacement of transmissions on physical uplinkshared channels (PUSCHs) with differing priorities, e.g., forultra-reliable low-latency communication (URLLC) and/or enhanced URLLC(eURLLC). In some embodiments, if (and/or when) a second PUSCHtransmission does not share a HARQ process ID with a first PUSCHtransmission (e.g., an existing PUSCH transmission), then any repetitionwith the first PUSCH transmission which overlaps with any portion of thesecond PUSCH transmission may be overridden. In some embodiments, if(and/or when) a second PUSCH transmission does not share a HARQ processID with a first PUSCH transmission (e.g., an existing PUSCHtransmission), then any repetition of the first PUSCH transmissionbetween an earliest repetition of the first PUSCH transmission whichoverlaps (e.g., time overlaps and/or overlaps in time) with any portionof the second PUSCH transmission and a last repetition of the firstPUSCH transmission which overlaps with any portion of the second PUSCHtransmission may be overridden. In other words, in some embodiments, allrepetitions (inclusive) between an earliest repetition and a latestrepetition of a first PUSCH transmission which overlap with any portionof a second PUSCH transmission may be dropped and/or omitted. In someembodiments, if (and/or when) a second PUSCH transmission shares a HARQprocess ID with a first PUSCH transmission (e.g., an existing PUSCHtransmission), then any repetition of the first PUSCH transmissionbetween an earliest repetition of the first PUSCH transmission whichoverlaps with any portion of the second PUSCH transmission and the lastrepetition of the first PUSCH transmission may be overridden.

For example, FIG. 13 illustrates examples of possible treatments ofcolliding transmissions, according to some embodiments. As shown, forscenarios in which a transmission associated with a configured grantPUSCH, configured as a single slot PUSCH, collides with a transmissionassociated with a dynamic grant PUSCH configured as a single slot PUSCH,a PUSCH with aggregation, and/or a PUSCH with repetition type A, a UE,such as UE 106, may follow 3GPP release 15 timing requirements and PUSCHrepetition type A may follow PUSCH with aggregation treatment, e.g., asdescribed above. Additionally, for scenarios in which a transmissionassociated with a configured grant PUSCH, configured as a PUSCH withrepetition and/or a PUSCH with repetition type A, collides with atransmission associated with a dynamic grant PUSCH configured as asingle slot PUSCH, a PUSCH with aggregation, and/or a PUSCH withrepetition type A, a UE, such as UE 106, may follow 3GPP release 15timing requirements and PUSCH repetition type A may follow PUSCH withaggregation treatment, e.g., as described above. In addition, forscenarios in which a transmission associated with a configured grantPUSCH, configured as a PUSCH with repetition type B, collides with atransmission associated with a dynamic grant PUSCH configured as asingle slot PUSCH, a PUSCH with aggregation, and/or a PUSCH withrepetition type A, a UE, such as UE 106, may follow 3GPP release 15timing requirements and a transmission associated with a dynamic grantPUSCH that collides with any portion of a transmission associated with aconfigured grant PUSCH may override the transmission associated with theconfigured grant PUSCH, e.g., as further described herein with referenceto FIGS. 14, 15, and 16 . Further, for scenarios in which a transmissionassociated with a configured grant PUSCH collides with a transmissionassociated with a dynamic grant PUSCH configured with PUSCH repetitiontype B, any transmission of the dynamic grant PUSCH that overlaps aportion of a transmission associated with the configure grant PUSCH mayoverride the transmission associated with the configured grant PUSCH,e.g., as further described herein with reference to FIGS. 14, 15, and 16.

In some embodiments, if (and/or when) all OFDM symbols in nominalrepetitions of a dynamic grant PUSCH with repetition type B are used inthe transmission, then the 3GPP release 15 overriding rules, asdiscussed above, may be used. In some embodiments, if (and/or when) atransmission associated with a single slot PUSCH overlaps with anynominal repetition of another PUSCH transmission configured with PUSCHrepetition type B, those two PUSCHs are considered to be overlapping(e.g., overlapping in time and/or time overlapping). In someembodiments, if (and/or when) a transmission associated with a singleslot PUSCH overlaps with at least one actual repetition of another PUSCHtransmission configured with PUSCH repetition type B, those two PUSCHsare considered to be overlapping. For example, as illustrated by FIG. 14, if (and/or when) a single slot configured grant PUSCH overlaps with atleast a portion of nominal repetitions of a dynamic grant PUSCH withrepetition type B, but does not overlap with any actual repetitions ofthe dynamic grant PUSCH with repetition type B, then a UE, such as UE106, may transmit on a configured grant within a single slot that doesnot overlap with an actual transmission of the dynamic grant PUSCH withrepetition type B.

In some embodiments, if (and/or when) a transmission associated with aconfigured grant PUSCH with slot aggregation and/or PUSCH repetitiontype A overlaps with at least a portion of nominal repetitions of adynamic grant PUSCH with repetition type B, but does not overlap withany actual repetitions of the dynamic grant PUSCH with repetition typeB, then a UE, such as UE 106, may transmit on a configured grant PUSCHwithin a slot that does not overlap with an actual transmission of thedynamic grant PUSCH with repetition type B. Note that symbol j (e.g., asdiscussed above) may be with respect to a first slot within which aconfigured grant PUSCH transmission overlaps with a dynamic grant PUSCHtransmission.

In some embodiments, if (and/or when) a transmission associated with asingle slot dynamic grant PUSCH overlaps with at least a portion ofnominal repetitions of a configured grant PUSCH with repetition type B,but does not overlap with any actual repetitions of the configured grantPUSCH with repetition type B, then a UE, such as UE 106, may transmit onthe dynamic grant PUSCH within a slot that does not overlap with anactual transmission of the configured grant PUSCH with repetition typeB. Note that symbol j (e.g., as discussed above) may be with respect toa first actual repetition among all the actual repetition of theconfigured grant PUSCH transmission which overlap with the dynamic grantPUSCH.

In some embodiments, if (and/or when) a transmission associated with aconfigured grant PUSCH with repetition type B overlaps with at least aportion of repetitions of a dynamic grant PUSCH with slot aggregationand/or PUSCH repetition type A, then a UE, such as UE 106, may transmiton a configured grant PUSCH within a slot that does not overlap with atransmission of the dynamic grant PUSCH with repetition type A, e.g., asillustrated by FIG. 15 . As shown in FIG. 15 , a configured grant PUSCHmay configure the UE to transmit CG-1 and CG-2 in a first slot (e.g.,slot n) and CG-3 and CG-4 in a second slot (e.g., slot n+1).Additionally, a dynamic grant PUCSH may configure the UE to transmitDG-1 in the first slot and DG-2 in the second slot. As shown, a UE, suchas UE 106, supporting interlaced transmissions, may transmit CG-1 andDG-1 in the first slot and CG-3 and DG-2 in the second slot. Thus, wherethe configured grant and dynamic grant overlap, the UE may transmit thedynamic grant. Further, where the configured grant and dynamic grant donot overlap, the UE may transmit the configured grant. In other words,each actual repetition in the configured grant PUSCH is checked againsteach actual repetition in the dynamic grant PUSCH on arepetition-by-repetition basis.

In some embodiments, if (and/or when) a transmission associated with aconfigured grant PUSCH with repetition type B overlaps with at least aportion of repetitions of a dynamic grant PUSCH with slot aggregationand/or PUSCH repetition type A, then a UE, such as UE 106, may transmiton any configured grant PUSCH that occurs prior to a transmission of thedynamic grant PUSCH with repetition type A, e.g., as illustrated by FIG.16 . As shown in FIG. 16 , a configured grant PUSCH may configure the UEto transmit CG-1 and CG-2 in a first slot (e.g., slot n) and CG-3 andCG-4 in a second slot (e.g., slot n+1). Additionally, a dynamic grantPUCSH may configure the UE to transmit DG-1 in the first slot and DG-2in the second slot. As shown, a UE, such as UE 106, not supportinginterlaced transmissions, may transmit CG-1 and DG-1 in the first slotand DG-2 in the second slot. Thus, where the configured grant anddynamic grant overlap, the UE may transmit the dynamic grant. Further,where the configured grant proceeds a first dynamic grant transmission,the UE may transmit the configured grant.

In some embodiments, if (and/or when) a transmission associated with aconfigured grant PUSCH with repetition type B overlaps with at least aportion of repetitions of a dynamic grant with PUSCH repetition type B,then a UE, such as UE 106, may transmit on a configured grant PUSCHwithin a slot that does not overlap with a transmission of the dynamicgrant PUSCH with repetition type B. Thus, where the configured grantPUSCH and dynamic grant overlap PUSCH, the UE may transmit on thedynamic grant PUSCH. Further, where the configured grant PUSCH anddynamic grant PUSCH do not overlap, the UE may transmit on theconfigured grant PUSCH. In other words, each actual repetition in theconfigured grant PUSCH is checked against each actual repetition in thedynamic grant PUSCH on a repetition-by-repetition basis.

In some embodiments, if (and/or when) a transmission associated with aconfigured grant PUSCH with repetition type B overlaps with at least aportion of repetitions of a dynamic grant PUSCH with PUSCH repetitiontype B, then a UE, such as UE 106, may transmit on any configured grantPUSCH that occurs prior to a transmission of the dynamic grant PUSCHwith repetition type B. Thus, where the configured grant PUSCH anddynamic grant PUSCH overlap, the UE may transmit on the dynamic grantPUSCH. Further, where the configured grant PUSCH proceeds a firstdynamic grant PUSCH transmission, the UE may transmit on the configuredgrant PUSCH.

In some embodiments, a PUSCH may be designated at one of two prioritylevels. A first priority level may be associated with low priorityand/or no priority (e.g., a PUSCH scheduled without a priority level,such as a PUSCH scheduled by DCI format 0_0, a configured grant PUSCHwith a configured grant configuration not configured with a physicallayer priority, and so forth). A second priority level may be associatewith a high priority. In some embodiments, in instances where aconfigured grant has the first priority level, the above described 3GPPrelease 15 timeline for dynamic grants may be maintained with repetitionby repetition overriding, e.g., to cover PUSCH repetition types A and B.Similarly, in some embodiments, in instances where a dynamic grant hasthe second priority level, the above described 3GPP release 15 timelinefor dynamic grants may be maintained with repetition by repetitionoverriding, e.g., to cover PUSCH repetition types A and B. In someembodiments, a configured grant with the second priority level mayoverride a priority dynamic grant with the first priority level. In someembodiments, such a rule (and/or condition) may be applied on arepetition by repetition basis, e.g., to cover PUSCH repetition types Aand B.

In some embodiments, Section 6.1 of 3GPP TS 38.214 Release 16 version 2may be modified to state that:

-   -   If a UE reports the capability of intra-UE prioritization, and        if a PUSCH corresponding to a configured grant and a PUSCH        scheduled by a PDCCH on a serving cell are partially or fully        overlapping in time,    -   If the PUSCH corresponding to the configured grant has priority        in configuredGrantConfig set to 1 (i.e., high priority), and the        PUSCH scheduled by the PDCCH is indicated as low priority by        having the priority indicator field in the scheduling DCI set to        0 or by not having the priority indicator field present in the        scheduling DCI, the UE is expected to transmit the PUSCH        corresponding to the configured grant, and drop the PUSCH        transmission scheduled by the PDCCH from the first symbol of the        repetition of the PUSCH transmission scheduled by the PDCCH        which overlaps with repetition(s) of the PUSCH corresponding to        the configured grant.    -   In case of PUSCH repetitions, the overlapping handling is        performed for each PUSCH repetition separately.    -   The UE is not expected to be scheduled for another PUSCH by a        PDCCH where this PUSCH starts no earlier than the end of the        prioritized transmitted PUSCH and before the end of the time        domain allocation of the cancelled PUSCH.

Further, in some embodiments, Section 6.1 of 3GPP TS 38.214 Release 16version 2 may be modified to state that:

-   -   If a UE reports the capability of intra-UE prioritization, and        if a PUSCH corresponding to a configured grant and a PUSCH        scheduled by a PDCCH on a serving cell are partially or fully        overlapping in time,    -   If the PUSCH corresponding to the configured grant has priority        in configuredGrantConfig set to 1 (i.e., high priority), and the        PUSCH scheduled by the PDCCH is indicated as low priority by        having the priority indicator field in the scheduling DCI set to        0 or by not having the priority indicator field present in the        scheduling DCI, the UE is expected to transmit the PUSCH        corresponding to the configured grant, and drop the PUSCH        transmission scheduled by the PDCCH from the first symbol of the        repetition of the PUSCH transmission scheduled by the PDCCH        which overlaps with repetition(s) of the PUSCH corresponding to        the configured grant.    -   In case of PUSCH repetitions, the overlapping handling is        performed for each PUSCH repetition separately if HPID of the        PUSCH corresponding to the configured grant is different from        the HPID of the PUSCH transmission scheduled by the PDCCH. If        the HPID of the PUSCH corresponding to the configured grant is        the same as the HPID of the PUSCH transmission scheduled by the        PDCCH, the PUSCH transmission scheduled by the PDCCH from the        first symbol of the repetition of the PUSCH transmission        scheduled by the PDCCH which overlaps with repetition(s) of the        PUSCH corresponding to the configured grant to the last symbol        of the last repetition of the PUSCH transmission scheduled by        the PDCCH is dropped.    -   The UE is not expected to be scheduled for another PUSCH by a        PDCCH where this PUSCH starts no earlier than the end of the        prioritized transmitted PUSCH and before the end of the time        domain allocation of the cancelled PUSCH.]

In some embodiments, assuming a first configured grant PUSCH and asecond configured grant PUSCH have the same physical layer priority, thesecond configured grant PUSCH may not be allowed to override the firstconfigured grant PUSCH, where a transmission occasion for the firstconfigured grant PUSCH occurs prior to a transmission occasion for thesecond configured grant PUSCH. Alternatively, in some embodiments, thesecond configured grant PUSCH may be allowed, in certain instances, tooverride the first configured grant PUSCH, where a transmission occasionfor the first configured grant PUSCH occurs prior to a transmissionoccasion for the second configured grant PUSCH. For example, a UE, suchas UE 106, may be prohibited from using the second configured grantPUSCH if (and/or when) a downlink HARQ process ID (HPID) would collidean HPID of the first configured grant PUSCH. As another example, a UE,such as UE 106, may use the second configured grant PUSCH if (and/orwhen) an HPID of the first configured grant PUSCH is the same as an HPIDof the second configured grant PUSCH. In such embodiments, starting froma first repetition of the first configured grant PUSCH among repetitionsof the first configured grant PUSCH overlapping with the secondconfigured grant PUSCH, remaining repetitions of the first configuredgrant PUSCH may be dropped. As a further example, a UE, such as UE 106,may perform repetition by repetition overlap handling.

In some embodiments, assuming a first configured grant PUSCH and asecond configured grant PUSCH have different physical layer priority,the fist configured grant PUSCH may be allowed, in certain instances, tooverride the second configured grant PUSCH. For example, a UE, such asUE 106, may be prohibited from using a second configured grant PUSCHwith the second priority level if (and/or when) an HPID of the secondconfigured grant PUSCH would collide with an HPID of a first configuredgrant PUSCH with the first priority level. As another example, a UE,such as UE 106, may use a second configured grant PUSCH with the secondpriority level if (and/or when) an HPID of the second configured grantPUSCH is the same as an HPID of a first configured grant PUSCH with thefirst priority level. In such embodiments, starting from a firstrepetition of the first configured grant PUSCH among repetitions of thefirst configured grant PUSCH overlapping with the second configuredgrant PUSCH, remaining repetitions of the first configured grant PUSCHmay be dropped. As a further example, a UE, such as UE 106, may performrepetition by repetition overlap handling.

Further, in some embodiments, Section 6.1 of 3GPP TS 38.214 Release 16version 2 may be modified to state that:

-   -   If a UE reports the capability of intra-UE prioritization, and        if a second PUSCH corresponding to a configured grant and a        first PUSCH corresponding to a configured grant on a serving        cell are partially or fully overlapping in time,    -   If the second PUSCH corresponding to the configured grant has        priority in configuredGrantConfig set to 1 (i.e., high        priority), and the first PUSCH corresponding to the configured        grant has priority in configuredGrantConfig set to 0 (i.e. low        priority) or no priority configuration, the UE is expected to        transmit the second PUSCH and drop the first PUSCH transmission        from the first symbol of the repetition of the first PUSCH        transmission which overlaps with repetition(s) of the second        PUSCH.    -   In case of PUSCH repetitions, the overlapping handling is        performed for each PUSCH repetition separately if HPID of the        second PUSCH is different from the HPID of the second PUSCH. If        the HPID of the second PUSCH is the same as the HPID of the        second PUSCH transmission, the first PUSCH transmission from the        first symbol of the repetition of the first PUSCH which overlaps        with repetition(s) of the second to the last symbol of the last        repetition of the first PUSCH transmission is dropped.    -   The UE is not expected to be scheduled for another PUSCH by a        PDCCH where this PUSCH starts no earlier than the end of the        prioritized transmitted PUSCH and before the end of the time        domain allocation of the cancelled PUSCH.]

As discussed above, nested transmissions may become problematic for botha UE and a base station. Thus, in some embodiments, a number of nestedlevels may be limited to X, where X may be configured by either a UE,such as UE 106, e.g., based on UE capabilities, and/or via higher layersignaling (e.g., a UE may provide a base station with UE capabilitiesand the base station may determine a value of X, e.g., based on the UEcapabilities and/or network traffic conditions). In some embodiments, upto X−1 levels of nested transmissions may be allowed for configuredgrant PUSCHs, e.g., such that one level remains for potentialtransmission for a dynamic grant PUSCH. In some embodiments, if (and/orwhen) in a radio system such as a radio system conforming to 3GPPrelease 17 in which high priority dynamic grant PUSCH may be allowed tooverride a low priority dynamic grant PUSCH, then X−2 levels may beallowed for configured grant PUSCHs, e.g., such that two levels arereserved for potential transmission(s) for a high priority dynamic grantPUSCH and/or a low priority dynamic grant PUSCH.

FIG. 17 illustrates a block diagram of an example of a method forselection of physical uplink shared channels (PUSCHs) with differingpriorities, according to some embodiments. The method shown in FIG. 17may be used in conjunction with any of the systems, methods, or devicesshown in the Figures, among other devices. In various embodiments, someof the method elements shown may be performed concurrently, in adifferent order than shown, or may be omitted. Additional methodelements may also be performed as desired. As shown, this method mayoperate as follows.

At 1702, a first PUSCH and a second PUSCH may be configured, e.g., by aUE, such as UE 106, e.g., the UE may determine resources fortransmission on the first PUSCH and the second PUSCH. In someembodiments, the first PUSCH may correspond to a configured grant. Insome embodiments, the second PUSCH may also correspond to a configuredgrant. In some embodiments, the second PUSCH may be scheduled by aphysical downlink control channel (PDCCH) on a serving cell. Thus, theUE may configure the first PUSCH (e.g., determine resources fortransmission on the first PUSCH) based on the configured grant.Similarly, the UE may configure the second PUSCH (e.g., determineresources for transmission on the second PUSCH) based on the scheduleprovided by the PDCCH on the serving cell and/or another configuredgrant. In other words, the UE may prepare transmission of first data ona first PUSCH resource based on the configured grant. Similarly, the UEmay prepare transmission of second data on a second PUSCH resource basedon the schedule provided by the PDCCH on the serving cell and/or anotherconfigured grant.

In some embodiments, the first PUSCH may be associated with a firstpriority level. Additionally, second PUSCH may be associated with asecond priority level. In such embodiments, the first priority level maybe associated with a high priority and the second priority level may beassociated with one of low priority or no priority. In some embodiments,the first PUSCH may be one of a PUSCH with slot aggregation, a PUSCHwith repetition type A, and/or a PUSCH with repetition type B. In someembodiments, the second PUSCH may be one of a PUSCH with slotaggregation, a PUSCH with repetition type A, or a PUSCH with repetitiontype B.

At 1704, the UE may determine a time overlap between at least onetransmission occasion of the first PUSCH with the second PUSCH. In otherwords, the UE may determine that at least one transmission occasionassociated with the first PUSCH overlaps in time (e.g., time overlaps)with at least one transmission occasion associated with the secondPUSCH.

At 1706, the UE may drop, based, at least in part, on a priority of thefirst PUSCH, transmissions (e.g., one or more transmissions) scheduledfor the second PUSCH. In some embodiments, the UE may determine that thepriority of the first PUSCH is higher than a priority of the secondPUSCH. In some embodiments, transmissions scheduled for the second PUSCHmay be dropped starting with a first symbol of a repetition of thesecond PUSCH which overlaps in time with one or more repetitions of thefirst PUSCH. In some embodiments, for each respective repetition of thesecond PUSCH, transmissions scheduled for the second PUSCH may bedropped starting with a first symbol of the respective repetition of thesecond PUSCH which overlaps in time with one or more repetitions of thefirst PUSCH.

In some embodiments, dropping transmissions scheduled for the secondPUSCH may include the UE determining whether a downlink hybrid automaticrepeat request (HARD) process identifier (HPID) of the first PUSCH isdifferent from an HPID of the second PUSCH. In such embodiments, inresponse to determining that the HPID of the first PUSCH is differentfrom the HPDI of the second PUSCH, the UE may drop, for each respectiverepetition of the second PUSCH, transmissions scheduled for the secondPUSCH starting with a first symbol of the respective repetition of thesecond PUSCH which overlaps in time with one or more repetitions of thefirst PUSCH. Additionally, in such embodiments, in response todetermining that the HPID of the first PUSCH is not different from theHPDI of the second PUSCH, the UE may drop transmissions scheduled forthe second PUSCH from a first symbol of a repetition of the second PUSCHwhich overlaps in time with one or more repetition of the first PUSCH toa last symbol of a last repetition of the second PUSCH.

In some embodiments, the UE may transmit at least a portion oftransmissions scheduled for the second PUSCH that do not time overlapwith transmissions scheduled for the first PUSCH. In some embodiments,the UE may skip at least a portion of transmissions scheduled for thesecond PUSCH that do not time overlap with transmissions scheduled forthe first PUSCH.

FIG. 18 illustrates another block diagram of an example of a method forselection of physical uplink shared channels (PUSCHs) with differingpriorities, according to some embodiments. The method shown in FIG. 18may be used in conjunction with any of the systems, methods, or devicesshown in the Figures, among other devices. In various embodiments, someof the method elements shown may be performed concurrently, in adifferent order than shown, or may be omitted. Additional methodelements may also be performed as desired. As shown, this method mayoperate as follows.

At 1802, a first PUSCH and a second PUSCH may be configured, e.g., by aUE, such as UE 106, e.g., the UE may determine resources fortransmission on the first PUSCH and the second PUSCH. In someembodiments, the first PUSCH may correspond to a configured grant andthe second PUSCH may be scheduled by a physical downlink control channel(PDCCH) on a serving cell. Thus, the UE may configure the first PUSCH(e.g., determine resources for transmission on the first PUSCH) based onthe configured grant. Similarly, the UE may configure the second PUSCH(e.g., determine resources for transmission on the second PUSCH) basedon the schedule provided by the PDCCH on the serving cell. In otherwords, the UE may prepare transmission of first data on a first PUSCHresource based on the configured grant. Similarly, the UE may preparetransmission of second data on a second PUSCH resource based on theschedule provided by the PDCCH on the serving cell.

In some embodiments, the first PUSCH may be associated with a firstpriority level. Additionally, the second PUSCH may be associated with asecond priority level. In such embodiments, the first priority level maybe associated with a high priority and the second priority level may beassociated with one of low priority or no priority. In some embodiments,the first PUSCH may be one of a PUSCH with slot aggregation, a PUSCHwith repetition type A, and/or a PUSCH with repetition type B. In someembodiments, the second PUSCH may be one of a PUSCH with slotaggregation, a PUSCH with repetition type A, or a PUSCH with repetitiontype B.

At 1804, the UE may determine a time overlap between at least onetransmission occasion of the first PUSCH with the second PUSCH. In otherwords, the UE may determine that at least one transmission occasionassociated with the first PUSCH overlaps in time (e.g., time overlaps)with at least one transmission occasion associated with the secondPUSCH.

At 1806, the UE may drop, based, at least in part, on a priority of thefirst PUSCH, transmissions (e.g., one or more transmissions) scheduledfor the second PUSCH. In some embodiments, the UE may determine that thepriority of the first PUSCH is higher than a priority of the secondPUSCH. In some embodiments, transmissions scheduled for the second PUSCHmay be dropped starting with a first symbol of a repetition of thesecond PUSCH which overlaps in time with one or more repetitions of thefirst PUSCH. In some embodiments, for each respective repetition of thesecond PUSCH, transmissions scheduled for the second PUSCH may bedropped starting with a first symbol of the respective repetition of thesecond PUSCH which overlaps in time with one or more repetitions of thefirst PUSCH.

In some embodiments, dropping transmissions scheduled for the secondPUSCH may include the UE determining whether a downlink hybrid automaticrepeat request (HARQ) process identifier (HPID) of the first PUSCH isdifferent from an HPID of the second PUSCH. In such embodiments, inresponse to determining that the HPID of the first PUSCH is differentfrom the HPDI of the second PUSCH, the UE may drop, for each respectiverepetition of the second PUSCH, transmissions scheduled for the secondPUSCH starting with a first symbol of the respective repetition of thesecond PUSCH which overlaps in time with one or more repetitions of thefirst PUSCH. Additionally, in such embodiments, in response todetermining that the HPID of the first PUSCH is not different from theHPDI of the second PUSCH, the UE may drop transmissions scheduled forthe second PUSCH from a first symbol of a repetition of the second PUSCHwhich overlaps in time with one or more repetition of the first PUSCH toa last symbol of a last repetition of the second PUSCH.

In some embodiments, the UE may transmit at least a portion oftransmissions scheduled for the second PUSCH that do not time overlapwith transmissions scheduled for the first PUSCH. In some embodiments,the UE may skip at least a portion of transmissions scheduled for thesecond PUSCH that do not time overlap with transmissions scheduled forthe first PUSCH.

FIG. 19 illustrates yet another block diagram of an example of a methodfor selection of physical uplink shared channels (PUSCHs) with differingpriorities, according to some embodiments. The method shown in FIG. 19may be used in conjunction with any of the systems, methods, or devicesshown in the Figures, among other devices. In various embodiments, someof the method elements shown may be performed concurrently, in adifferent order than shown, or may be omitted. Additional methodelements may also be performed as desired. As shown, this method mayoperate as follows.

At 1902, a first PUSCH and a second PUSCH may be configured, e.g., by aUE, such as UE 106. In some embodiments, the first PUSCH may correspondto a first configured grant and the second PUSCH may correspond to asecond configured grant. Thus, the UE may configure the first PUSCH(e.g., determine resources for transmission on the first PUSCH) based onthe first configured grant. Similarly, the UE may configure the secondPUSCH (e.g., determine resources for transmission on the second PUSCH)based on the second configured grant. In other words, the UE may preparetransmission of first data on a first PUSCH resource based on the firstconfigured grant. Similarly, the UE may prepare transmission of seconddata on a second PUSCH resource based on the second configured grant.

In some embodiments, the first PUSCH may be associated with a firstpriority level. Additionally, second PUSCH may be associated with asecond priority level. In such embodiments, the first priority level maybe associated with a high priority and the second priority level may beassociated with one of low priority or no priority. In some embodiments,the first PUSCH may be one of a PUSCH with slot aggregation, a PUSCHwith repetition type A, and/or a PUSCH with repetition type B. In someembodiments, the second PUSCH may be one of a PUSCH with slotaggregation, a PUSCH with repetition type A, or a PUSCH with repetitiontype B.

At 1904, the UE may determine a time overlap between at least onetransmission occasion of the first PUSCH with the second PUSCH. In otherwords, the UE may determine that at least one transmission occasionassociated with the first PUSCH overlaps in time (e.g., time overlaps)with at least one transmission occasion associated with the secondPUSCH.

At 1906, the UE may drop, based, at least in part, on a priority of thefirst PUSCH, transmissions (e.g., one or more transmissions) scheduledfor the second PUSCH. In some embodiments, the UE may determine that thepriority of the first PUSCH is higher than a priority of the secondPUSCH. In some embodiments, transmissions scheduled for the second PUSCHmay be dropped starting with a first symbol of a repetition of thesecond PUSCH which overlaps in time with one or more repetitions of thefirst PUSCH. In some embodiments, for each respective repetition of thesecond PUSCH, transmissions scheduled for the second PUSCH may bedropped starting with a first symbol of the respective repetition of thesecond PUSCH which overlaps in time with one or more repetitions of thefirst PUSCH.

In some embodiments, dropping transmissions scheduled for the secondPUSCH may include the UE determining whether a downlink hybrid automaticrepeat request (HARQ) process identifier (HPID) of the first PUSCH isdifferent from an HPID of the second PUSCH. In such embodiments, inresponse to determining that the HPID of the first PUSCH is differentfrom the HPDI of the second PUSCH, the UE may drop, for each respectiverepetition of the second PUSCH, transmissions scheduled for the secondPUSCH starting with a first symbol of the respective repetition of thesecond PUSCH which overlaps in time with one or more repetitions of thefirst PUSCH. Additionally, in such embodiments, in response todetermining that the HPID of the first PUSCH is not different from theHPDI of the second PUSCH, the UE may drop transmissions scheduled forthe second PUSCH from a first symbol of a repetition of the second PUSCHwhich overlaps in time with one or more repetition of the first PUSCH toa last symbol of a last repetition of the second PUSCH.

In some embodiments, the UE may transmit at least a portion oftransmissions scheduled for the second PUSCH that do not time overlapwith transmissions scheduled for the first PUSCH. In some embodiments,the UE may skip at least a portion of transmissions scheduled for thesecond PUSCH that do not time overlap with transmissions scheduled forthe first PUSCH.

It is well understood that the use of personally identifiableinformation should follow privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining the privacy of users. In particular,personally identifiable information data should be managed and handledso as to minimize risks of unintentional or unauthorized access or use,and the nature of authorized use should be clearly indicated to users.

Embodiments of the present disclosure may be realized in any of variousforms. For example, some embodiments may be realized as acomputer-implemented method, a computer-readable memory medium, or acomputer system. Other embodiments may be realized using one or morecustom-designed hardware devices such as ASICs. Still other embodimentsmay be realized using one or more programmable hardware elements such asFPGAs.

In some embodiments, a non-transitory computer-readable memory mediummay be configured so that it stores program instructions and/or data,where the program instructions, if executed by a computer system, causethe computer system to perform a method, e.g., any of the methodembodiments described herein, or, any combination of the methodembodiments described herein, or, any subset of any of the methodembodiments described herein, or, any combination of such subsets.

In some embodiments, a device (e.g., a UE 106) may be configured toinclude a processor (or a set of processors) and a memory medium, wherethe memory medium stores program instructions, where the processor isconfigured to read and execute the program instructions from the memorymedium, where the program instructions are executable to implement anyof the various method embodiments described herein (or, any combinationof the method embodiments described herein, or, any subset of any of themethod embodiments described herein, or, any combination of suchsubsets). The device may be realized in any of various forms.

Any of the methods described herein for operating a user equipment (UE)may be the basis of a corresponding method for operating a base station,by interpreting each message/signal X received by the UE in the downlinkas message/signal X transmitted by the base station, and eachmessage/signal Y transmitted in the uplink by the UE as a message/signalY received by the base station.

Although the embodiments above have been described in considerabledetail, numerous variations and modifications will become apparent tothose skilled in the art once the above disclosure is fully appreciated.It is intended that the following claims be interpreted to embrace allsuch variations and modifications.

What is claimed is:
 1. A method for selection of physical uplink sharedchannels (PUSCHs), comprising: determining that at least a firsttransmission corresponding to a first PUSCH associated with a configuredgrant would overlap in time with at least a second transmissioncorresponding to a second PUSCH scheduled by downlink controlinformation (DCI); and based on whether a hybrid automatic repeatrequest (HARQ) process identifier (HPID) of the first PUSCH is differentfrom an HPID of the second PUSCH, selectively dropping transmissionrepetitions scheduled for the first PUSCH or transmission repetitionsscheduled for the second PUSCH, starting with a symbol at which atransmission repetition begins to overlap with transmissions of theother PUSCH.
 2. The method of claim 1, wherein, when the HPID of thefirst PUSCH is different from the HPID of the second PUSCH and apriority of the first PUSCH is higher than a priority of the secondPUSCH, selectively dropping transmission repetitions scheduled for thefirst PUSCH or transmission repetitions scheduled for the second PUSCH,starting with the symbol at which the transmission repetition begins tooverlap with transmissions of the other PUSCH comprises droppingtransmission repetitions scheduled for the second PUSCH starting with afirst symbol of a respective repetition of the second PUSCH whichoverlaps in time with one or more transmissions of the first PUSCH. 3.The method of claim 2, further comprising: transmitting at least aportion of transmissions scheduled for the second PUSCH that do not timeoverlap with transmissions scheduled for the first PUSCH.
 4. The methodof claim 2, further comprising: skipping at least a portion oftransmissions scheduled for the second PUSCH that do not time overlapwith transmissions scheduled for the first PUSCH.
 5. The method of claim1, wherein, when the HPID of the first PUSCH is not different from theHPID of the second PUSCH, selectively dropping transmission repetitionsscheduled for the first PUSCH or transmission repetitions scheduled forthe second PUSCH, starting with the symbol at which the transmissionrepetition begins to overlap with transmissions of the other PUSCHcomprises dropping transmission repetitions for the first PUSCH startingfrom a first symbol of a repetition of the first PUSCH which overlaps intime with one or more transmissions of the second PUSCH.
 6. The methodof claim 1, further comprising: configuring the first PUSCH and thesecond PUSCH.
 7. The method of claim 1, wherein the first PUSCH is oneof a PUSCH with slot aggregation, a PUSCH with repetition type A, or aPUSCH with repetition type B.
 8. The method of claim 1, wherein thesecond PUSCH is one of a PUSCH with slot aggregation, a PUSCH withrepetition type A, or a PUSCH with repetition type B.
 9. An apparatus,comprising: a memory; and a processing element in communication with thememory, wherein the processing element is configured to: determine thatat least a first transmission corresponding to a first PUSCH associatedwith a configured grant would overlap in time with at least a secondtransmission corresponding to a second PUSCH scheduled by downlinkcontrol information (DCI); and based on whether a hybrid automaticrepeat request (HARQ) process identifier (HPID) of the first PUSCH isdifferent from an HPID of the second PUSCH, selectively droptransmission repetitions scheduled for the first PUSCH or transmissionrepetitions scheduled for the second PUSCH, starting with a symbol atwhich a transmission repetition begins to overlap with transmissions ofthe other PUSCH.
 10. The apparatus of claim 9, wherein, when the HPID ofthe first PUSCH is different from the HPID of the second PUSCH and apriority of the first PUSCH is higher than a priority of the secondPUSCH, to selectively drop transmission repetitions scheduled for thefirst PUSCH or transmission repetitions scheduled for the second PUSCH,starting with the symbol at which the transmission repetition begins tooverlap with transmissions of the other PUSCH, the processing element isfurther configured to drop transmission repetitions scheduled for thesecond PUSCH starting with a first symbol of a respective repetition ofthe second PUSCH which overlaps in time with one or more transmissionsof the first PUSCH.
 11. The apparatus of claim 10, wherein theprocessing element is further configured to: transmit at least a portionof transmissions scheduled for the second PUSCH that do not time overlapwith transmissions scheduled for the first PUSCH.
 12. The apparatus ofclaim 10, wherein the processing element is further configured to: skipat least a portion of transmissions scheduled for the second PUSCH thatdo not time overlap with transmissions scheduled for the first PUSCH.13. The apparatus of claim 9, wherein, when the HPID of the first PUSCHis not different from the HPID of the second PUSCH, to selectively droptransmission repetitions scheduled for the first PUSCH or transmissionrepetitions scheduled for the second PUSCH, starting with the symbol atwhich the transmission repetition begins to overlap with transmissionsof the other PUSCH, the processing element is further configured to droptransmission repetitions for the first PUSCH starting from a firstsymbol of a repetition of the first PUSCH which overlaps in time withone or more transmissions of the second PUSCH.
 14. The apparatus ofclaim 9, wherein the processing element is further configured to:configure the first PUSCH and the second PUSCH.
 15. A user equipmentdevice (UE), comprising: at least one antenna; at least one radio,wherein the at least one radio is configured to perform cellularcommunication using at least one radio access technology (RAT); and oneor more processors coupled to the at least one radio, wherein the one ormore processors and the at least one radio are configured to performvoice and/or data communications; wherein the one or more processors areconfigured to cause the UE to: determine that at least a firsttransmission corresponding to a first PUSCH associated with a configuredgrant would overlap in time with at least a second transmissioncorresponding to a second PUSCH scheduled by downlink controlinformation (DCI); and based on whether a hybrid automatic repeatrequest (HARD) process identifier (HPID) of the first PUSCH is differentfrom an HPID of the second PUSCH, selectively drop transmissionrepetitions scheduled for the first PUSCH or transmission repetitionsscheduled for the second PUSCH, starting with a symbol at which atransmission repetition begins to overlap with transmissions of theother PUSCH.
 16. The UE of claim 15, wherein, when the HPID of the firstPUSCH is different from the HPID of the second PUSCH and a priority ofthe first PUSCH is higher than a priority of the second PUSCH, toselectively drop transmission repetitions scheduled for the first PUSCHor transmission repetitions scheduled for the second PUSCH, startingwith the symbol at which the transmission repetition begins to overlapwith transmissions of the other PUSCH, the one or more processors arefurther configured to cause the UE to drop transmission repetitionsscheduled for the second PUSCH starting with a first symbol of arespective repetition of the second PUSCH which overlaps in time withone or more transmissions of the first PUSCH.
 17. The UE of claim 16,wherein the one or more processors are further configured to cause theUE to: transmit at least a portion of transmissions scheduled for thesecond PUSCH that do not time overlap with transmissions scheduled forthe first PUSCH.
 18. The UE of claim 16, wherein one or more processorsare further configured to cause the UE to: skip at least a portion oftransmissions scheduled for the second PUSCH that do not time overlapwith transmissions scheduled for the first PUSCH.
 19. The UE of claim15, wherein, when the HPID of the first PUSCH is not different from theHPID of the second PUSCH, to selectively drop transmission repetitionsscheduled for the first PUSCH or transmission repetitions scheduled forthe second PUSCH, starting with the symbol at which the transmissionrepetition begins to overlap with transmissions of the other PUSCH, theone or more processors are further configured to cause the UE to droptransmission repetitions for the first PUSCH starting from a firstsymbol of a repetition of the first PUSCH which overlaps in time withone or more transmissions of the second PUSCH.
 20. The UE of claim 15,wherein one or more processors are further configured to cause the UEto: configure the first PUSCH and the second PUSCH.